This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Crash Monitoring
Roger Yang edited this page Feb 2, 2021
·
27 revisions
- The main goal here is not to file an issue for every single distinct crash report. But to find regressions or new problems that need to be addressed.
- Once you're familiar with the process this should not take more than 10 mins in the morning.
- Since we are focused on Java crashes, Sentry currently is the better choice.
- Ignore
level:info
issues (blue labels in Sentry). These issues are informational only.
- Look at Sentry Fenix-nightly overview. Go though trending issues. https://sentry.prod.mozaws.net/operations/firefox-nightly/dashboard/
- Look at Sentry custom search https://sentry.prod.mozaws.net/operations/firefox-nightly/?query=is%3Aunresolved+level%3Afatal+level%3Aerror
- Crashes that have level either Fatal or Error.
- Crashes that are occurring on latest Fenix and A-C versions.
- Crashes that are spiking.
- Crashes that are new.
- Crashes that happen repeatedly and often.
- Is this a crash due to a recent change? If so, contact the developer.
- The histogram on the right side can help determine this along with checking the Firefox-Beta and Firefox Sentry products
- Triage the crash to determine if the issue is real and requires a Github issue to track it.
- When filing an issue add a link to the issue as a comment in the Sentry crash for the products (nightly, beta, release) where the crash appears
- If a Github issue is required to track the crash, put the issue in the staging board. https://github.com/orgs/mozilla-mobile/projects/70
- If you recently landed a new module / change that is significant, contact the crash monitor so they are aware of it.
- Look at https://crash-stats.mozilla.org/topcrashers/?product=Fenix&version=0.0a1&days=3&_range_type=build for reports on Nightly builds.
- This will return zero results if GV build ID is greater than 3 days old. Change to the 7 day view and ask #releaseduty-mobile in Slack about the GV upgrade task being broken
- Ignore [INFO] issues
- Use Sentry, Github and Bugzilla to determine if the crash has already been reported.
- If the crash is new and the volume is high then consider raising an issue.
- If the crash is a Native crash file a bug using the crash-stats Bugzilla tab from a crash ID
- If the crash is a Java crash then consider opening an issue in Github.