Sentry
Last updated
Was this helpful?
Last updated
Was this helpful?
is an application monitoring platform that helps developers identify, debug, and resolve issues.
Integrating Sentry with Cortex allows you to:
, giving you insight into your entity's operational maturity
, using the Cortex Slack Bot
Create that include rules related to Sentry errors
Before getting started:
Create a in your Sentry user settings.
The user auth token requires Read
for the Issue & Event and Project scopes.
In Cortex, navigate to the :
In Cortex, click your avatar in the lower left corner, then click Settings.
Under "Integrations," click Sentry.
Click Add configuration.
Configure the integration form:
Auth token: Enter the auth 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
).
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.
If your Sentry projects don't cleanly match the Cortex entity tag, you can override this in the Cortex entity descriptor.
You can define projects under the x-cortex-sentry
block:
name
Project name as defined in Sentry
✓
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.
With the Sentry integration, you can create Scorecard rules and write CQL queries based on Sentry projects.
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:
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.
By default, Cortex will use the (e.g., my-entity
) as the best guess for Sentry projects. For example, if your entity tag is my-entity
, then the corresponding project in Sentry should also be my-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 .
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 . Cortex will pull in the title and tags for each issue.
If you have also configured the , you can use the command /cortex sentry <tag>
in to get a list of all recent Sentry issues for a given entity. tag
is the in Cortex.
See more examples in the in Cortex.
Counts Sentry events for a given to a max of 1,000.
Email: , or open a support ticket in the in app Resource Center