# Incident core types: incident.io

Incident core types provides a unified, reliable way to ingest, view, and analyze data from incident providers, starting with incident.io Get a single source of truth for all your incidents with full support in CQL, Scorecards, and Engineering Intelligence.

{% hint style="info" %}
Incident core types is currently only availible for incident.io customers. We will be migrating all incident providers to the new system over the coming months!
{% endhint %}

### What's new

The Incident core type introduces a centralized approach to incident data in Cortex:

* **Unified incident catalog**: View all incidents across your organization in one place, with rich metadata including severity, status, affected entities, and more.
* **Entity-level incident visibility**: See active incidents directly on entity pages and quickly identify which services are currently impacted
* **Full CQL support**: Write rules and queries using incident data with the new `incidents` and `oncall` CQL expressions.
* **Multiple data sources**: Ingest incidents from incident.io via our integration platform, or push custom incident data via API,
* **Engineering Intelligence integration**: Access incident metrics you rely on today, now powered by a single, consistent data pipeline.

### Viewing incidents

#### Incident Catalog

Access the Incident Catalog from the main navigation by going to [All entities](https://app.getcortexapp.com/admin/entities) --> [Entity types](https://app.getcortexapp.com/admin/entities?activeTab=types) --> [Incident](https://app.getcortexapp.com/admin/definitions/cortex-incident) to see all incidents across your organization.

<figure><img src="/files/jkGU4zFhymtHapo8l8Mi" alt=""><figcaption></figcaption></figure>

The Incident Catalog displays the following information with the default view sorted by most recently opened incidents first.

| Column        | Description                                 |
| ------------- | ------------------------------------------- |
| Incident name | The title of the incident                   |
| Severity      | The severity level assigned to the incident |
| Status        | Current status (e.g., Active, Resolved)     |
| Opened at     | When the incident was created               |

**Note:** Cortex ingests all available incidents from incident.io. Incidents marked as [declined or merged](https://docs.incident.io/incidents/triaging) or [canceled](https://docs.incident.io/incidents/delete-incidents#can-i-delete-or-hide-an-incident) are treated as deleted in Cortex and will not appear in your catalog or contribute to scorecards.

#### Incident detail page

Click on any incident in the catalog to view its full details, including:

* Complete incident metadata
* All affected entities
* Link to the source system
* Entity YAML
* Entity relationships

#### Incidents on entity pages

Entity pages include incident information in two places:

* **Overview tab**: Active incidents are prominently displayed at the top of the page
* **Incidents tab**: View a complete list of incidents for that entity

### Using incident data

#### CQL expressions

The new `incidents` CQL categories let you write powerful queries and Scorecard rules based on incident data.

See the [CQL documentation](https://app.getcortexapp.com/admin/queries) for the complete list of available incident expressions.

#### Scorecards

Create Scorecard rules using incident-based CQL expressions to track operational health:

* Ensure services have had no critical incidents in the past 30 days
* Verify mean time to resolution meets your SLOs
* Check that all production services have on-call schedules configured

#### Engineering Intelligence

Incident metrics available in Engineering Intelligence are now powered by the same unified data pipeline, ensuring consistency across all Cortex features. The following metrics are supported:

* Incident frequency
* Mean time to resolution (MTTR)

## Upcoming enhancements

We plan to develop additional capabilities during and beyond the beta period:

* Support for on-call as a core type
* Support for incident.io follow up items
* Additional incident provider integrations (PagerDuty, Rootly, and more)
* Enhanced incident analytics


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cortex.io/resources/beta/incident-core-types-incident.io-private-beta.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.