Skip to main content
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.
Sentry is an application monitoring platform that helps developers identify, debug, and resolve issues. Integrating Sentry with Cortex allows you to:

​
How to configure Sentry with Cortex

​
Prerequisites

Before getting started:
  • Create a personal token in your Sentry user settings.
    • The token requires Read permissions for the Issue & Event and Project scopes.

​
Configure the integration in Cortex

  1. In Cortex, navigate to the Sentry settings page:
    • Click Integrations from the main nav. Search for and select Sentry.
  2. Click Add configuration.
  3. Configure the integration form:
    • Auth token: Enter the personal token you generated in Sentry.
    • Organization slug: Enter your Sentry organization slug.
      • You can find this in your Sentry URL, e.g., https://sentry.io/organizations/{SLUG}/issues/.
    • Host: If using a self-hosted Sentry instance, enter the URL here without the API path (e.g., bugsnag.getcortexapp.com).
  4. Click Save.
After saving your configuration, you are redirected to the Sentry integration settings page in Cortex. In the upper right corner of the page, click Test configuration to ensure Sentry was configured properly.

​
How to connect Cortex entities to Sentry projects

​
Discovery

By default, Cortex will use the Cortex tag (e.g., my-entity) as the best guess for Sentry projects. For example, if your Cortex tag is my-entity, then the corresponding project in Sentry should also be my-entity. If your Sentry projects don’t cleanly match the Cortex tag, you can override this in the Cortex entity descriptor.

​
Editing the entity descriptor

You can define projects under the x-cortex-sentry block:

​
Using the Sentry integration

​
Viewing Sentry errors on an entity

Error data will appear on an entity’s details page. In an entity’s sidebar, click Error tracking to view detected issues for each Sentry project. At the top of the page, see a list of Sentry projects associated with an entity. Each project listed in Cortex links back to the project details page in Sentry. Under the Issues header on the Error tracking page, you’ll find a list of all issues related to the projects that Cortex detected in Sentry. Each issue in the list links back to that issue’s details page in Sentry. Cortex will pull in the title and tags for each issue. Events Sentry issues and events will also appear in an entity’s event timeline, found under Events in the sidebar. This allows users to contextualize Sentry issues with other key data - like deploys or errors discovered from other integrations - during incidents or migrations.

​
Retrieving issues in Slack

If you’ve also configured the Slack integration, you can ask the AI Assistant for an entity’s recent Sentry issues. Mention @Cortex in a channel or direct message and ask a question like “Show me recent Sentry issues for payments-api,” identifying the entity by its Cortex tag. For setup and usage details, refer to Using the AI assistant.

​
Scorecards and CQL

With the Sentry integration, you can create Scorecard rules and write CQL queries based on Sentry projects. See more examples in the CQL Explorer in Cortex.
Check if entity has a registered Sentry project.Definition: sentry (==/!=) nullExampleFor a production readiness Scorecard, you can use this expression to make sure entities are linked to a Sentry project.
This can also serve as a way to confirm that entities are synced with Sentry and reporting frequently.
Counts Sentry events for a given custom query to a max of 1,000.If no query is provided, the rule will count unresolved events by default.Definition: sentry.numOfIssueEvents((<query>))ExampleFor a Scorecard focused on operational maturity, you can check for any unresolved issues that were first seen within a week.
Counts Sentry issues for a given custom query to a max of 300.If no query is provided, the rule will count unresolved issues by default.Definition: sentry.numOfIssues((<query>))ExampleFor a Scorecard focused on operational maturity, you can pull in the number of Sentry issues to make sure entities are functioning as expected.
For a Scorecard focused on code quality, you can write a more focused rule to make sure there haven’t been any issues in production environments in the last week.
The maximum number of Sentry events fetched for any query is 1,000, while the maximum number of issues fetched is 300.

​
View integration logs

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.
Click into a row to get more information, including time stamp, status code, full error, and request path.

​
Still need help?↗

The following options are available to get assistance from the Cortex Customer Engineering team:
  • Email: help@cortex.io, or open a support ticket in the in app Resource Center
  • Slack: Users with a connected Slack channel will have a workflow added to their account. From here, you can either @CortexTechnicalSupport or add a :ticket: reaction to a question in Slack, and the team will respond directly.
Don’t have a Slack channel? Talk with your Customer Success Manager.
Last modified on September 9, 2026