Skip to main content

What is Cortex?

Cortex is an Internal Developer Portal that helps engineering teams manage their service catalog, track service ownership, measure reliability, and improve operational excellence.

Integration Overview

The Rootly + Cortex integration is bidirectional, meaning data flows in both directions to create a seamless experience:

How It Works

Cortex → Rootly (Service Sync)

Rootly imports your service catalog from Cortex, making Cortex the source of truth for services. What gets synced:
  • Service entities from your Cortex catalog
  • Service names and descriptions
  • Service metadata and tags
Set up Cortex → Rootly integration →

Rootly → Cortex (Incident Display)

Cortex pulls incident data from Rootly and displays it within your Internal Developer Portal. What you can do:
  • View active incidents on service pages in Cortex
  • Create Rootly incidents directly from Cortex
  • Build scorecards based on Rootly incident metrics
  • Track service reliability using incident data
Learn about Rootly → Cortex integration →

Key Benefits

Unified Service Catalog

Use Cortex as your single source of truth for service definitions. When you update a service in Cortex, the changes automatically flow to Rootly, ensuring consistency across your incident management workflow.

Reduced Context Switching

Developers and on-call engineers can stay in Cortex while accessing incident information. Create incidents, check incident history, and view operational metrics without switching tools.

Automated Service Ownership

Leverage Cortex’s ownership data to automatically route incidents to the right teams. When an incident affects a service, Rootly knows exactly who owns it based on Cortex’s catalog.

Data-Driven Reliability

Build Cortex scorecards using Rootly incident data to measure and improve service reliability. Track MTTR, incident frequency, and operational maturity across all your services.

Which Integration Do I Need?

Both! The integrations work together to provide the complete experience:
If you want to…You need…
Keep service definitions in syncCortex → Rootly
View incidents in Cortex portalRootly → Cortex
Link incidents to Cortex servicesCortex → Rootly
Create incidents from CortexRootly → Cortex
Build reliability scorecardsRootly → Cortex
The Cortex → Rootly integration is configured in Rootly. The Rootly → Cortex integration is configured in Cortex and maintained by the Cortex team.

Getting Started

Step 1: Sync Services from Cortex

Start by setting up the Cortex → Rootly integration to import your service catalog. This ensures incidents can be properly linked to services.

Step 2: Display Incidents in Cortex

Next, configure the Rootly → Cortex integration in Cortex to display incident data within your portal.

Step 3: Leverage the Combined Power

Once both directions are configured:
  • Services in Rootly stay in sync with Cortex
  • Incidents in Rootly appear on service pages in Cortex
  • Teams can work from either tool seamlessly

Support

For Service Sync (Cortex → Rootly)

This integration is built and maintained by Rootly.

For Incident Display (Rootly → Cortex)

This integration is built and maintained by Cortex.
I