Monitor the stability of your application and measure progress against stability targets.
Stability is a measure of the proportion of application sessions that are error free. It is calculated using session information and errors reported from your application, and is available on the Standard and Enterprise plans.
Application stability is shown on your:
The stability score shows you the percentage of user sessions that were error free. The color indicates how this 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|
For each project, you set the two stability targets you want to monitor
Set your stability targets in Project settings.
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.
Your notifier must be configured to enable session tracking and see the stability score for your releases. See your platform’s docs for details.
Each notifier has its own default definition of a session. In general:
|Platform type||Session definition|
|Mobile||An app is opened|
|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.