Skip to main content




Bugsnag monitors application stability. You can use Bugsnag to drive insights into values such as:

  • Outstanding errors
  • Error frequency


In order to connect Cortex to your Bugsnag instance, you’ll need to create a Bugsnag Auth Token, and add it under Settings → Bugsnag.


If you do not see the Settings page you're looking for in the sidebar, you likely don't have the proper permissions and need to contact your admin.

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 whitelist our static IP, you can route requests through a secondary proxy in your network that has this IP whitelisted, and have that proxy route traffic to your Bugsnag instance.



By default, Cortex will use the entity tag (e.g. my-service) as the "best guess" for the Bugsnag project key. For example, if your entity tag is my-service, then the corresponding project key in Bugsnag should also be my-service.

If your Bugsnag project keys don’t cleanly match the Cortex entity tag, you can override this in the Cortex Catalog Descriptor.

Catalog descriptor

If you need to override the automatic discovery, you can define the following block in your Cortex Catalog Descriptor.

project: my-project # projectKey in Bugsnag

The value for project should be the project's slug as defined in Bugsnag.