In this guide, you'll learn how to set up and configure the Sentry integration in Cortex to enhance visibility into events and issues.
Auth token: The user auth token created in Sentry.
Organization slug: Slug for your Sentry organization, which can be found in Sentry settings and in the URL for your instance (e.g. https://sentry.io/organizations//issues/
).
Host: Optional host name for self-hosted Sentry instances. Do not include the /api
prefix.
If you’ve set everything up correctly, you’ll see the option to Remove Integration in settings.
You can also use the Test configuration button to confirm that the configuration was successful. If your configuration is valid, you’ll see a banner that says “Configuration is valid. If you see issues, please see documentation or reach out to Cortex support.”
name
Project name as defined in Sentry
✓
Once the integration with Sentry is established, you'll be able to find key data about errors and issues on an entity's details page. In the entity's sidebar, navigate to Error tracking > Sentry to find detected issues for each project.
At the top of the page, you'll find 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, you'll find a list of all issues related to the project(s) 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 side panel. This allows users to contextualize Sentry issues with other key data - like deploys or errors discovered from other integrations - during incidents or migrations.
You can use the /cortex sentry
command in Slack, where `` is the entity tag in Cortex, to get a list of all recent Sentry issues for a given entity.
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.
The maximum number of Sentry events fetched for any query is 1,000, while the maximum number of issues fetched is 300.
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
Chat: Available in the 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.