Open
Bug 1355938
Opened 8 years ago
Updated 2 years ago
Monitor uptake for Firefox Screenshots system add-on
Categories
(Firefox :: General, enhancement)
Firefox
General
Tracking
()
NEW
People
(Reporter: ckprice, Unassigned)
References
Details
User Story
I would like to know general uptake to ensure that Screenshots is being deployed and installed as expected. Some questions for Beta are 1) What percent of Beta users have Firefox Screenshots installed? 2) What percent of the users who have Firefox Screenshots installed, also have `extensions.screenshots.system-disabled=FALSE`? 3) What percent of the users who have Firefox Screenshots installed, have `extensions.screenshots.user-disabled=TRUE`? 4) What is the real time uptake of Firefox Screenshots? (e.g. https://pipeline-cep.prod.mozaws.net/dashboard_output/graphs/analysis.moz_telemetry_doctype_error_ratio_monitor.tls_13_study_v4.html)
Attachments
(1 file)
|
58 bytes,
text/plain
|
Details |
This is created to make sure we are carefully monitoring uptake for the Firefox Screenshots system add-on
|
Reporter | |
Updated•8 years ago
|
Blocks: firefox-screenshots
|
|
Reporter | |
Updated•8 years ago
|
User Story: (updated)
|
|
Reporter | |
Comment 1•8 years ago
|
||
This graph represents User Story 1. I kept getting `Error running query: Could not communicate with the remote task. The node may have crashed or be under too much load. This is probably a transient issue, so please retry your query in a few minutes. ` so the graphs are from the query I forked it from.
|
|
Reporter | |
Comment 2•8 years ago
|
||
rhelmer noted that we may be able to use main_summary to get data in 24 hours instead of waiting for 7 days for longitudinal (comment 1).
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•