-
Notifications
You must be signed in to change notification settings - Fork 119
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
Evaluate moving to Sentry from BugSnag #1318
Comments
Sentry have java lib with example available here |
Sentry approved Flank for an open source account! I can add the team once we're ready to work on this |
Sentry have java library Initialization
Bugsnag(API_KEY)
Sentry.init {
it.dsn = DNS_URL
} Logging errors
bugsnag?.notify(error)
Sentry.captureException(error) Additional dataWe can set
Events can be filtered by user, tag, event level. This feature can be helpful when we need to find a specific issue for a specific system. We login errors to
I think we can also log: Flank version, os name, and WDYT? |
That sounds awesome |
Fixes #1318 ## Test Plan > How do we know the code works? 1. Flank should display session id below ```revision``` 2. Should save session id to ```session_id.txt``` in matrix path 3. Should upload ```session_id.txt``` when ```disable-results-upload``` not set 4. Unit & Integration tests should pass ## Checklist - [X] Save and upload session id - [X] Unit tested - [X] Integration tests updated
Author the user story for this feature
As a Flank developer, I want to understand crashes in Flank so I can fix them.
Describe the solution
Evaluate Sentry as a BugSnag alternative.
The text was updated successfully, but these errors were encountered: