Releases dashboard

Compare the health of the releases of your application.

The releases dashboard is used to compare the health of releases of your application using the crash rate and information about errors in each release. The releases dashboard is available on the Pro plan.

Identifying releases

Releases are automatically created from errors and sessions that are reported by your application. For example if an error is reported from version 1.0.0 of your application from the production release stage, a release will be created for that version in Bugsnag.

Releases can be enriched with source control information and more by using a build tool integration.

Crash rate

The crash rate for a release is calculated as the percentage of sessions that experience an unhandled error. The color indicates how this crash rate compares to other releases of your app that have been in use over the last 7 days.

Crash rate indicator Definition
Average rash rate This release has an average or below average crash rate
Above average crash rate This release has a crash rate up to 20% higher than the average
High crash rate This release has a crash rate more than 20% higher than the average


Your notifier must be configured to enable session tracking and see the crash rate for your releases. See your platform’s docs for details.

Each notifier has it’s own default definition of a session. In general:

Platform type Session definition
Mobile An app is opened
JavaScript (Browser) A page is loaded
Server-side A request is processed

Alternatively you can provide your own definition of a session using the sessionStart() function or equivalent for your platform.

Source control

Each release can link to your source control provider to show the code that is was used to build a version and the changes from the previous version. To use this feature you will need to use a build tool integration.

Released by

Each release displays the person or entity who built the application. This can be useful to identify the ‘owner’ of a release. To use this feature you will need to use a build tool integration.


Other metadata that is relevant to a build can be seen on the detailed view of a release. This can be used to display any application specific information that is associated with a build, for example parameters that were used to build the application, and details of the changes contained in the build. To use this feature you will need to use a build tool integration.