Cortex connects to many third-party vendors whose system interfaces frequently change. As a result, integration behavior or configuration steps may shift without notice. If you encounter unexpected issues, check with your system administrator or refer to the vendor’s documentation for the most current information. Additionally, integration sync times vary and are subject to scheduling overrides and timing variance.
Why use the integration for Rootly
Rootly is an on-call and incident response platform. The integration brings that data into Cortex, so an entity’s incident history and current on-call coverage sit alongside its ownership, dependencies, and Scorecard results. The integration for Rootly brings the following into Cortex:- Incidents - Active and historical incidents for an entity, with severity, status, and affected entities. Requires the Incidents category.
- On-call schedules - Who’s on call now and who’s on call next for an entity. Requires the On-call category.
Setting up Rootly’s Cortex integration first
Rootly has its own Cortex integration, configured from the Rootly side, that syncs your Cortex catalog into Rootly. When it’s set up, each Rootly service carries the ID of its matching Cortex entity, and Cortex uses that ID to map Rootly incidents to the right entities. This is the most reliable way to connect the two platforms, so set it up before you configure the integration in Cortex. See Rootly’s Cortex integration docs for setup instructions.Configuring Rootly
Prerequisites
- Users with the
Configure Integrationspermission can configure Rootly. - Create an API token in Rootly. Make sure the Rootly user account represented by the token has admin permissions in Rootly.
Installing Rootly in Cortex
- From the main sidebar, expand Integrations, then select Configurations.
- Locate Rootly, then click Install. The Rootly side panel opens.
- In the Rootly side panel, do the following:
-
From the Category dropdown, select the types of data to import (required):
- Incidents - Imports incidents with severity, status, and affected entities.
- On-call - Imports on-call schedules, including who’s on call now and next.
- Under Configuration alias, enter the alias you’ll use to tie entity registrations to different configuration accounts (required).
- Under API token, enter your Rootly API token (required).
-
From the Category dropdown, select the types of data to import (required):
- Click Test connection. A successful connection means your integration is configured correctly.
- Click Save.
To modify an existing configuration, see Modifying an integration configuration.
If you configured Rootly in Cortex before October 27, 2026, your configuration has been moved to the new integration automatically, and you don’t need to set it up again. To bring in on-call data, make sure the On-call category is selected on your configuration. See Changing categories on an existing configuration.
Using multiple Rootly configurations
The Rootly integration supports multiple configurations. To add another:- From the main sidebar, expand Integrations, then select Configurations.
- Locate Rootly, then click Settings.
- In the upper-right corner of the page, click Add configuration.
- Follow the steps in Installing Rootly in Cortex above.
- From the main sidebar, expand Integrations, then select Configurations.
- Locate Rootly, then click Settings.
- Click the pencil icon next to a configuration.
- Toggle on Set as default. If you only have one configuration, it’s automatically set as the default.