Main crash rate missing from mission-control dashboard -> nightly -> windows
Categories
(Cloud Services :: Mission Control, defect)
Tracking
(Not tracked)
People
(Reporter: ritu, Unassigned)
Details
Attachments
(2 files)
Screenshot_2019-01-22 windows nightly.png
I don't see mission control report main crash rate for Nightly build.
|
Reporter | |
Comment 1•5 years ago
|
||
Hi Will, do you know why this might be happening?
|
||
Comment 2•5 years ago
|
||
Earlier data some data was showing, here is a screenshot: https://drive.google.com/file/d/17tL1XNJObcLS-4ZWyKM-MAYbMXMtUJKX/view
|
|
Reporter | |
Comment 3•5 years ago
|
||
|
||
Comment 4•5 years ago
|
||
Hmm, I'm not exactly sure what happened, things are back to normal now. Searching new relic for errors, it appears that we ran into a bunch of problems fetching version data from product-details.mozilla.org around the time this was bug was reported:
https://rpm.newrelic.com/accounts/1402187/applications/139827211/traced_errors
That could explain why we weren't updating and thus lost the measure? Not entirely sure.
I don't think we actually need to use product-details anymore now that we're using buildhub to get version data-- tempted to just address that and hope it was the cause of this problem, as I'm not sure what else to investigate. We're probably going to be switching out the data store that mission control uses in the next few quarters, which would be the other probable cause of this error.
Leaving NI open until I do up the patch.
|
|
||
Comment 5•5 years ago
|
||
Just realized that we still need product-details (or something like it), because a new release might appear on buildhub before it is actually the current one. I think what we actually need to do here is provide more information when a service that mission control depends on isn't working, see bug 1523316 for that.
I'm going to mark this one as incomplete, because I'm not sure what else can be done here.
Description
•