Repository navigation
[request for feedback] Release Health (session tracking) #4466
Description
Hey Sentry JS world!
What do you think about our Release Health (session tracking) product for Javascript applications?
We want to improve our JS release health data, to make the release health feature more useful for JS developers.
So let us hear it - the good, the bad, and the ugly! 😄
- Is the release health feature useful to you?
- If not then why?
- Are we collecting the right kind of data? Do we communicate the health of your app in a way that is meaningful?
- What additional metrics might you want to see, to track the health of a Javascript release?
- Are the answers to the above different between Node and browser, or in different frameworks?
Examples:
-
If we stick with the idea of crash-free sessions, what should count as a “crash” (especially for web apps, considering that browsers don’t provide a good API for capturing when a tab hard-crashes)? There is no clear fix, but we'd like to hear your thoughts.
-
Right now we mark error events as “handled” or “unhandled” (with tags and in the UI of the issue stream). Do you pay attention to this, and find the distinction helpful? If you do, what are your use cases?
Maybe you haven't seen or tried out Release Health yet? Now is a great time.
https://sentry.io/resources/release-health-by-sentry/
https://docs.sentry.io/platforms/javascript/configuration/releases/
Activity
danielasy commentedon Jan 31, 2022
Hello! I'm currently looking into front-end health metrics, so I'm very interested in Release Health.
I'm a fairly recent user though. We have a few small apps using it, and I'm going to test it against larger projects with more events and issues in the next weeks.
However, some questions popped up while I was reading the docs and exploring the dashboard. Some of them have to do with how we already track errors, some of them with how crashes and "handled" vs "unhandled" work. Please bear with me if I've missed something in the way :)
level:fatalseverity, so we can query these issues separately and treat them with priority, but we lack visibility in how much they're affecting sessions and users.I'll share more impressions once I get Release Health going in more projects. In the meanwhile, I'd welcome any insight about these points!