Many `invalid_value` errors noticed in Fenix for metrics `power.total_thread_wakeups` and `power.wakeups_per_process_type` starting March 30 or so
Categories
(Toolkit :: Performance Monitoring, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox99 | --- | unaffected |
firefox100 | --- | fixed |
firefox101 | --- | fixed |
People
(Reporter: chutten, Assigned: florian)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
48 bytes,
text/x-phabricator-request
|
diannaS
:
approval-mozilla-beta+
|
Details | Review |
In the Monday Glean SDK Weekly Monitoring meeting we noticed a rising number of invalid_value
errors for the metrics power.total_thread_wakeups
and power.wakeups_per_process_type
.
Having a look at the code it can record 0
which is not a happy value for a Glean counter
metric (at least not yet, see bug 1762859). This is somewhat different from how the cpu time metrics do things.
Probably just needs a quick if (newWakeups)
or something.
Reporter | ||
Updated•3 years ago
|
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Set release status flags based on info from the regressing bug 1759535
Updated•3 years ago
|
Assignee | ||
Comment 2•3 years ago
|
||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Comment 4•3 years ago
|
||
bugherder |
Comment 5•3 years ago
|
||
The patch landed in nightly and beta is affected.
:florian, is this bug important enough to require an uplift?
If not please set status_beta
to wontfix
.
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 6•3 years ago
|
||
(In reply to Release mgmt bot [:suhaib / :marco/ :calixte] from comment #5)
The patch landed in nightly and beta is affected.
:florian, is this bug important enough to require an uplift?
If not please setstatus_beta
towontfix
.
I don't know, hopefully Chutten will know.
Reporter | ||
Comment 7•3 years ago
|
||
The data's quality is unaffected by 0s not being recorded, so this is a matter of getting accurate error counts inside the error reporting mechanism when it hits release (and making our error monitoring plots easier to read)...
Since this is such a straightforward change, I would like this uplifted to make those plots easier to read.
Assignee | ||
Comment 8•3 years ago
|
||
Comment on attachment 9272080 [details]
Bug 1764113 - avoid incrementing thread wakeup glean counters by 0, r=gerald.
Beta/Release Uplift Approval Request
- User impact if declined: No user impact, but Glean errors from the release channel will be harder to count (see comment 7)
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Trivial patch, only adding an
if
block to avoid recording invalid values. - String changes made/needed: None
Comment 9•3 years ago
|
||
Comment on attachment 9272080 [details]
Bug 1764113 - avoid incrementing thread wakeup glean counters by 0, r=gerald.
Approved for 100.0b9
Comment 10•3 years ago
|
||
bugherder uplift |
Description
•