New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add sentry session tracking #4157
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #4157 +/- ##
==========================================
+ Coverage 82.63% 82.66% +0.02%
==========================================
Files 256 256
Lines 32608 32610 +2
==========================================
+ Hits 26945 26956 +11
+ Misses 5663 5654 -9
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this easy?? sick!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
Problem:
We have information about failures seen by wandb library users but we don't have a good way of knowing the percentage of users that encounter a given problem. The goal is to calculate a problem rate metric:
ProblemRate = NumberOfUsersExperiencingAProblem / TotalNumberOfUsers
The service sentry.io collects problems, and number of users. but we have a blind spot within sentry about total number of users. We have other data sources which we could use to get this denominator but then the way data is being captured could be inconsistent. The larger project to work on this is/will be: Internal Notion Doc
Sentry has two endpoints we would like to use:
Currently we are only using the store endpoint.
Envelope can be used to send session informaiton.
Caveats:
Partially answered questions:
Possible future changes:
TODO:
Requires:
Testing
Will be tested with yea
Checklist