With Sentry, we can monitor the health of releases by observing user adoption, usage of the application, percentage of crashes, and session data. The primary component that Sentry uses to monitor health is called a session, which represents the interaction between the user and the application. For our view powered front end, this session is automatically initialized when we initialized the SDK. Thus, whenever the application is visited, the session begins.
If you visit a new browser tab, the session ends. But, going back to the application starts the session again. Awesome! Let's take a look at what information this provides for us in the dashboard.
Release Help is about releases. So, as you'd expect, this information can be found on the Releases page. Right here in the list of releases, we can already start to see some of the release health data. The adoption rate tells us how many users are using the new release.
The crash free rate is the percentage of sessions that did not result in the application crashing. Crashing is defined as an explicit unhandled error or hard crash. io that captured this event. Errors that did not cause the end of the application aren't included.
Finally, you can see the number of new issues raised during the release. Alright, let's click into the release now and you can see this information in even more detail. Here we have a chart of that crash-free session rate. We've also got a chart for sessions adopted, users adopted, and we've got some project release details such as when it was created, what version it's on, what package, and so on and so forth.
If we scroll down, we can also see all the exact issues that have occurred within this release. The more your application is used, and the more data this entry can collect, the more useful these release pages will be. And you'll be coming here for information, often. With Sentry, we can monitor the health of releases by observing user adoption, usage of the application, percentage of crashes, and session data.
The primary component that Sentry uses to monitor health is called a session, which represents the interaction between the user and the application. For our view powered front end, this session is automatically initialized when we initialized the SDK. Thus, whenever the application is visited, the session begins. If you visit a new browser tab, the session ends.
But, going back to the application starts the session again. Awesome! Let's take a look at what information this provides for us in the dashboard. Release Help is about releases.
So, as you'd expect, this information can be found on the Releases page. Right here in the list of releases, we can already start to see some of the release health data. The adoption rate tells us how many users are using the new release. The crash free rate is the percentage of sessions that did not result in the application crashing.
Crashing is defined as an explicit unhandled error or hard crash. io that captured this event. Errors that did not cause the end of the application aren't included. Finally, you can see the number of new issues raised during the release.
Alright, let's click into the release now and you can see this information in even more detail. Here we have a chart of that crash-free session rate. We've also got a chart for sessions adopted, users adopted, and we've got some project release details such as when it was created, what version it's on, what package, and so on and so forth. If we scroll down, we can also see all the exact issues that have occurred within this release.
The more your application is used, and the more data this entry can collect, the more useful these release pages will be. And you'll be coming here for information, often.