Closed
Bug 1515664
Opened 5 years ago
Closed 5 years ago
Investigate a decrease in release crash ping submissions
Categories
(Data Platform and Tools :: General, enhancement)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: trink, Unassigned)
References
Details
The count has been dropping/alerting all week and is now 70% below the previous week https://pipeline-cep.prod.mozaws.net/dashboard_output/graphs/analysis.moz_telemetry_doctype_monitor_crash.volume.html
Comment 1•5 years ago
|
||
Pretty sure this is just the results of the fix for bug 1498942 making its way into release. You can see that we went from 25 events of this kind per 1000 usage down to around ~1 from 63 -> 64: https://data-missioncontrol.dev.mozaws.net/#/release/windows We saw a similar pattern on the beta channel after this landed :chutten and I had a discussion about this yesterday on mission control irc channel: https://mozilla.logbot.info/missioncontrol/20181220#c15748097
Comment 2•5 years ago
|
||
I took a look at nightly shutdownkill volumes: https://sql.telemetry.mozilla.org/queries/60652#156515 The first cliff is the build where bug 1498942 landed, so that certainly seems to be the likely culprit. Non-content-shutdown crash pings are so infrequent on nightly since November that it's tricky to say, but I'm pretty sure they didn't show a similar effect (https://sql.telemetry.mozilla.org/queries/60689/source#156621). This suggests that the reduction in shutdownkill crashes is almost certainly the cause of the volume cliff.
See Also: → 1498942
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•2 years ago
|
Component: Pipeline Ingestion → General
You need to log in
before you can comment on or make changes to this bug.
Description
•