Monitor the stability of your application and measure progress against stability targets.
Stability features are available on Standard and Enterprise plans.
Stability is a measure of the proportion of user application sessions that are error free. It is calculated using session information and errors reported from your application.
There are two measures of stability score:
User stability is the percentage of users who were error free within a given day. Where user stability is shown over a longer time period than one day it is the aggregation of daily error free users.
An anonymous device identifier generated by BugSnag is used to detect unique users and is independent of user information that you can configure. Therefore a user who opens an app then logs in will be treated as a single user for stability calculations.
User stability is not available for server side projects.
Session stability is the percentage of user sessions that were error free over the time period.
Configure your stability targets in Project settings.
Choose whether you want to set targets for either user stability or session stability by selecting the stability target type.
Selecting user stability is recommeneded if you track other user-based business metrics for your app.
Select the two levels of stability target:
The stability target indicator shows you how your stability score compares to the targets you’ve set for your project.
|Stability score indicator||Definition|
|This release has a higher stability score than your target stability|
|The stability score of this release is between the target stability and critical stability|
|This release has a lower stability score than your critical stability|
Configure the daily or weekly stability summary emails to be alerted on how your project is performing against your stability targets. See stability summary emails.
Any session in which a user experiences an “unhandled” error is considered a crashing session and will impact the stability score. Different types of unhandled errors can cause different impacts on a user: usually it will mean the app has shut down completely but some unhandled errors on some platforms are recoverable.
It’s possible for a single session to have more than one unhandled error, but it will only count as one crashed session in the stability score.
All unhandled errors events visible in the dashboard will impact the stability score, including those that are snoozed or ignored.
Rate limited events are not collected by BugSnag. Any rate limited unhandled error events will not be counted towards the stability score.
Each notifier has its own default definition of a session. In general:
|Platform type||Session definition|
|Mobile||An app is opened or returned to after 30s or more in the background|
|Server-side||A request is processed|
Alternatively you can provide your own definition of a session using the
startSession() function or equivalent for your platform.