Stability

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:

Stability score

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.

  • The Stability Center shows a 30-day stability score which is based on the total number of sessions and errors over that time period.
  • The Releases dashboard show stability over the lifetime of a single release.
Stability score indicator Definition
Average stability score This release has a higher stability score than your target stability
Below average stability score The stability score of this release is between the target stability and critical stability
Low stability score This release has a lower stability score than your critical stability

Stability targets

For each project, you set the two stability targets you want to monitor

  • Target stability: This is the stability score that your team aims to exceed. Any score higher than this should mean that your app is in great shape and you should continue building new features for your users.
  • Critical stability: This critical stability target is the lower threshold of what is an acceptable stability score for your app. If you fall below this target, you’ll want to focus on fixing bugs to improve your app’s stability.

Set your stability targets in Project settings.

Errors that impact stability

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.

Reporting sessions

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
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.