BugSnag
Last updated
Last updated
is an application stability monitoring platform that provides error tracking and analytics. By integrating BugSnag with Cortex, you can view errors alongside other key metrics and gain greater understanding into your entities' operational maturity.
In this guide, you'll learn how to set up and use the BugSnag integration to drive insights into values such as:
Outstanding errors
Error frequency
In order to connect Cortex to your BugSnag instance, you’ll first need to create a in the My Account section of .
Once you've created the auth token, you can configure the integration in Cortex from the .
To configure the integration, provide the following information:
Auth token: Auth token generated from BugSnag
Organization slug: BugSnag organization for your instance; you can find this in settings or in your BugSnag URL (https://app.bugsnag.com/organizations//stability-center
)
Host (optional): URL for your BugSnag instance without the API path (e.g. bugsnag.getcortexapp.com
)
This is only needed if you're using a custom/self-hosted BugSnag instance
If you're using a self-hosted instance of BugSnag, you'll need to verify that your Cortex instance is able to reach the BugSnag instance. We route our requests through a static IP address. Reach out to support at to receive details about our static IP. If you're unable to directly allowlist our static IP, you can route requests through a secondary proxy in your network that has this IP allowlisted and have that proxy route traffic to your BugSnag instance.
project
Project key defined in BugSnag
✓
Once the integration with BugSnag is established, you'll be able to pull in error data to an entity's details page. You can find the total number of detected errors and a full list on the Error tracking page in the side panel.
With the BugSnag integration, you can create Scorecard rules and write CQL queries based on BugSnag errors.
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.
Each error in the list will display with an Error
, Info
, or Warning
tag based on the applied to a given error in BugSnag.
See more examples in the in Cortex.
To set a more specific standard, you can also create a rule based on a .
Email: , or open a support ticket in the in app Resource Center