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

# Rootly to Cortex

> View Rootly incident data inside Cortex and trigger incidents directly from your Internal Developer Portal to keep developers in their day-to-day tooling.

This integration brings incident management capabilities directly into your Cortex Internal Developer Portal.

<Info>
  This integration is built and maintained by the Cortex team. For setup instructions, visit [Cortex's integration documentation](https://docs.cortex.io/docs/reference/integrations/rootly).
</Info>

## Setup

This integration is configured entirely within Cortex. Visit the [Cortex integration setup guide](https://docs.cortex.io/docs/reference/integrations/rootly) for detailed installation instructions.

**You'll need:**

* Cortex admin permissions
* Rootly admin or owner permissions
* A Rootly API key (generated during Cortex setup)

## Features

### Trigger Incidents from Cortex

Create Rootly incidents directly from service pages in Cortex without switching tools.

**How it works:**
From any service page in Cortex, click the Rootly action to create a new incident. The incident is created in Rootly with the service context already attached.

### View Incident Data in Cortex

See real-time incident information directly on service entity pages in your Cortex catalog.

**What you can see:**

* Active incidents affecting the service
* Recent incident history
* Incident severity and status
* Links to detailed incident pages in Rootly

### Build Scorecards with Incident Data

Create custom scorecards and write CQL queries using Rootly incident data to measure service reliability.

**Example use cases:**

* Track MTTR (Mean Time to Resolution) per service
* Measure incident frequency and severity trends
* Score services based on operational maturity
* Set goals for reducing critical incidents

### Incident Catalog View

Rootly is the only incident management platform that appears in Cortex's catalog list view, giving you a unified perspective of both services and active incidents.

## Use Cases

### Platform Engineering Teams

Your platform team maintains dozens of internal services. When checking service health in Cortex, you want to immediately see if there are any active incidents.

**Solution**: Incident status appears directly on service pages. If an issue arises, you can create a Rootly incident without leaving Cortex.

### SRE Teams

You're conducting a service reliability review and need to understand incident patterns across services.

**Solution**: Use Cortex scorecards powered by Rootly data to visualize MTTR, incident frequency, and severity trends. Create CQL queries to track improvement over time.

### On-Call Engineers

You're paged about a service issue and need to quickly understand service dependencies and recent incident history.

**Solution**: Open the service in Cortex to see ownership, dependencies, and recent Rootly incidents all in one place. Create follow-up incidents directly from the context you're already in.

## Best Practices

### Keep Service Mappings Accurate

Ensure services in Cortex are properly mapped to services in Rootly for accurate incident association. Consistent naming helps maintain the connection.

### Leverage Scorecards

Create scorecards that track operational metrics like:

* Incidents per service per week
* Mean time to resolution
* Percentage of incidents with retrospectives
* Critical incident frequency

### Use Incident Context

When creating incidents from Cortex, include relevant service context in the incident description to help responders quickly understand the situation.

### Review Historical Trends

Regularly review incident data in Cortex to identify services that may need architectural improvements or additional monitoring.

## Support

The Cortex team built and actively maintains this integration.

**For help:**

* Email: [help@cortex.io](mailto:help@cortex.io)
* Documentation: [Cortex Rootly Integration Docs](https://docs.cortex.io/docs/reference/integrations/rootly)

**For Rootly API questions:**

* Visit the [Rootly API documentation](https://rootly.com/docs/api)
* Contact Rootly support through your account