Closed
Bug 1661015
Opened 5 years ago
Closed 5 years ago
[Profile counter] The telemetry ping never gets over 10
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
firefox82 | --- | affected |
People
(Reporter: obotisan, Unassigned)
References
(Blocks 2 open bugs)
Details
Affected versions
- Ubuntu 82.0a1
Affected platforms
- Windows 10 x64
- Windows 7 x64
Steps to reproduce
- Install Firefox 82.0a1.
- Create 12 profiles and run each of them for at least 30 seconds in the bacground.
- Navigate to about:telemetry, go to the Scalars and search for 'browser.engagement.profile_count'.
Expected result
- The telemetry ping is 12.
Actual result
- The telemetry ping never gets over 10.
Regression range
- This is not a refression.
Suggested severity
- S2
Reporter | ||
Updated•5 years ago
|
Has Regression Range: --- → no
Has STR: --- → yes
Comment 1•5 years ago
|
||
This is actually the desired behavior. In most cases, we don't need exact numbers of profiles. So for larger numbers of profiles, we bucket the values to better comply with our principle of lean data collection. This means that values of 10-99 will be reported as 10, values of 100-999 will be reported as 100, values of 1000-9999 will be reported as 1000, and all values above 9999 will be reported as 10000.
I see that the test plan specifies that this value should be 12, which I didn't catch. I'll leave a comment in that document mentioning it.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•