> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cortex.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Using the integration for Rootly

> [!NOTE]
>
> 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.

This article explains how to use the integration for Rootly. For configuration instructions, see [Configuring the integration for Rootly](https://docs.cortex.io/ingesting-data-into-cortex/integrations/rootly). For instructions on connecting Rootly to entities, see [Connecting entities to Rootly](https://docs.cortex.io/ingesting-data-into-cortex/integrations/rootly/connecting-entities-to-rootly.md).

## Viewing incident data

You can view incident data in the incident list and on an [entity's details page](https://docs.cortex.io/ingesting-data-into-cortex/entities-overview/entities/details.md).

### Incident list

See every incident across your organization in one place, with metadata including severity, status, and affected entities.

![](https://mintcdn.com/cortex-290c0c42/HbTtnyKVq-sSUnnp/images/incident-list.png?fit=max\&auto=format\&n=HbTtnyKVq-sSUnnp\&q=85\&s=13c406f0ee0dd97f918e37745856beb8)

**To access the incident list**:

1. From the main sidebar, expand **Integrations**, then select **Data**.
2. Select the **Incidents** tab.

The list is sorted by most recently opened incidents first.

#### Searching across and filtering the incident list

There are several ways to search and filter the list:

* To find specific incidents, use the search bar in the upper-right corner of the page and type to search.
* By default, the list sorts by most recently opened incident. Click **Opened** to reverse the order, or click **Name** to sort alphabetically instead.
* Click **Filter** to narrow down your list by date range, severity level, or status.

### Incidents on an entity's details page

View incidents in the following places on an entity's details page:

* On the **Overview** tab; active incidents are prominently displayed at the top of the page

  ![](https://mintcdn.com/cortex-290c0c42/HbTtnyKVq-sSUnnp/images/incidents-overview.png?fit=max\&auto=format\&n=HbTtnyKVq-sSUnnp\&q=85\&s=47597d54e017259b6923ed5d2cb541c2)
* In the left details sidebar, locate **Connections**, then select **Incidents**

  ![](https://mintcdn.com/cortex-290c0c42/HbTtnyKVq-sSUnnp/images/incidents-side-panel.png?fit=max\&auto=format\&n=HbTtnyKVq-sSUnnp\&q=85\&s=d81efeab515878e496af6c2a8c1ecda7)

## Viewing on-call information

### On-call shift data

View all on-call shifts ingested via the Rootly integration in a single place. This allows you to see exactly what data Cortex has brought in from the integration and what entities it's been linked to within Cortex.

**To access the on-call list**:

1. From the main sidebar, expand **Integrations**, then select **Data**.
2. Select the **On-call shifts** tab.
3. Do one of the following:
   * Select the **All** tab to view all on-call shifts in your workspace.
   * Select the **Mine** tab to view only your on-call shifts.

The list is sorted alphabetically by schedule name. Click a row to open a side panel showing who's on call now, who's on call next, and the teams the schedule is associated with.

![](https://mintcdn.com/cortex-290c0c42/HbTtnyKVq-sSUnnp/images/incident-on-call-tab.png?fit=max\&auto=format\&n=HbTtnyKVq-sSUnnp\&q=85\&s=d05a263f674f93fd29034b6c1fe71bf9)

#### Searching across and sorting the on-call list

To search and sort the list:

* Use the search bar in the upper-right corner of the page and type to search.
* By default, the list sorts alphabetically by schedule name. Click **Name** to sort from Z to A.

### On-call on an entity's details page

View current on-call information in the following places on an entity's details page:

* In the metadata sidebar in the **On-call now** block

  ![](https://mintcdn.com/cortex-290c0c42/IxDb4qc9F4yJyBqi/images/oncall-block.png?fit=max\&auto=format\&n=IxDb4qc9F4yJyBqi\&q=85\&s=143d3323e83228e4fd2ca4446c66c567)
* In the left details sidebar, locate **Connections**, then select **On-call**
  * Click a row to open a side panel showing who's on call now, who's on call next, and the teams the schedule is associated with.

    ![](https://mintcdn.com/cortex-290c0c42/0i_zoxXu6S5DvfC0/images/rootly-on-call.png?fit=max\&auto=format\&n=0i_zoxXu6S5DvfC0\&q=85\&s=3d5e63066c7feceeb755410455032ae1)

### Engineering homepage

View upcoming on-call rotations in the **My on-calls** block on your engineering homepage. Cortex shows on-call schedules up to six months out.

![](https://mintcdn.com/cortex-290c0c42/kB9I5hpwwMkz0yx1/images/homepage-oncalls.png?fit=max\&auto=format\&n=kB9I5hpwwMkz0yx1\&q=85\&s=891e6100fa27f48736a6b006120304fc)

## Creating Scorecard rules with Rootly data

### Incident expressions

CQL lets you write rules and queries against incident data. See the [CQL documentation](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20explorer\&path=Integrations\&path=Rootly) for the complete list of available incident expressions.

> [!NOTE]
>
> Create Scorecard rules using incident-based CQL expressions to track operational health. Common Scorecard rules built on incident data include:
>
> * Ensure services have had no critical incidents in the past 30 days.
> * Verify mean time to resolution meets your SLOs.

### On-call expressions

CQL lets you write rules and queries against on-call data. See the [CQL documentation](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20explorer\&path=Integrations\&path=Rootly\&path=On-call) for the complete list of available on-call expressions.

> [!NOTE]
>
> Create Scorecard rules using on-call based CQL expressions to track operational readiness, for example:
>
> * Verify that all production services have an on-call schedule configured.
> * Ensure critical services have on-call coverage before go-live.

## Incident metrics in Eng Intelligence

Incident metrics in [Eng Intelligence](https://docs.cortex.io/improve/eng-intelligence) are powered by the same unified data pipeline as the incident list, so the numbers stay consistent across Cortex. Eng Intelligence supports the following incident metrics:

* Incident frequency
* Mean time to resolution (MTTR)

## Viewing Rootly integration logs

> [!NOTE]
>
> This feature is available in Cortex cloud.

While viewing an integration's settings page, select the **Error logs** tab to view errors from the last 7 days. You can filter the logs list by configuration and by operation (for example, you could filter to view errors surfaced only via Scorecards).

![The 'Logs' tab on an integration's settings page shows error information over the past 7 days.](https://mintcdn.com/cortex-290c0c42/ovmDVVMNC2L6Yw7I/images/integration-error-logs.png?fit=max\&auto=format\&n=ovmDVVMNC2L6Yw7I\&q=85\&s=dffdc901a9ce0232aedd090bb3a4531c)

Click into a row to get more information, including time stamp, status code, full error, and request path.

## Troubleshooting and FAQ

> **I connected Rootly but no on-call data appears on my entity**
>
> Check that the **On-call** category is selected on your Rootly configuration. Then confirm the entity is connected to Rootly on-call: through a Rootly service that matches the entity, through a schedule's owning team, or through a `SCHEDULE` or `TEAM` registration. A Rootly schedule only has on-call coverage once an escalation policy in Rootly points to it, and a service only shows on-call if it has an escalation policy. If a schedule shows no coverage in Rootly, it won't show any in Cortex either.

> **I registered a team but see no schedules**
>
> A `TEAM` registration maps every schedule owned by that team in Rootly. If the team doesn't own any schedules, nothing maps. Register the schedule directly instead.

> **An incident exists in Rootly but doesn't appear on the entity in Cortex**
>
> Check that the incident lists the affected service in Rootly. Then confirm the service matches the entity, either through the Cortex ID from Rootly's Cortex integration, a service name that matches the entity's Cortex tag, or an `x-cortex-rootly` registration in the entity descriptor. Cortex doesn't automatically match on service slugs.


## Related topics

- [Rootly](https://docs.cortex.io/ingesting-data-into-cortex/integrations/rootly.md)
- [Connecting entities to Rootly](https://docs.cortex.io/ingesting-data-into-cortex/integrations/rootly/connecting-entities-to-rootly.md)
- [Using the integration for Kubernetes](https://docs.cortex.io/ingesting-data-into-cortex/integrations/kubernetes/using-the-integration-for-kubernetes.md)