Closed Bug 742903 Opened 10 years ago Closed 10 years ago
Verify Telemetry evolution data
The Telemetry evolution data is generated by aggregating data from the elastic search database. We need an automated way to verify that the Telemetry evolution data is correct. Put another way, we need a check on the job that aggregates the data. Bug 742897 is related in that in it I request that we verify the data in the elastic search database. How can we verify that the Telemetry evolution data is valid?
Marking: in group of > 33 asks for Telemetry that need PM priority before triage/scheduling.
Status: NEW → ASSIGNED
Whiteboard: [Telemetry] → Telemetry -- needs PM project priority
Whiteboard: Telemetry -- needs PM project priority → [Telemetry:P1]
Specific JIRA https://metrics.mozilla.com/projects/browse/METRICS-832
Whiteboard: [Telemetry:P1] → [Telemetry:P1] migrated to JIRA
New JIRA migration identifier - 55 BZ issues being considered in current planning for Q3
Target Milestone: Unreviewed → Targeted - JIRA
We currently are doing the following test for Telemetry Evolution data: - existence of data for 3 days ago; - existence of aurora data between 3 and 10 days ago and variation d-3/d-10; - existence of nightly data between 3 and 10 days ago and variation d-3/d-10 Also we have some more test for representative measures, such as: - CYCLE_COLLECTOR; - GC_REASON; - FX_TAB_ANIM_OPEN_MS; - CACHE_OFFLINE_SEARCH; - FX_NEW_WINDOW_MS where we test if there is any data 3 days ago, but on this I think it's best if we had some feedback, namely what are the (most important) measures that you want to be tested.
This has been in place and working great for a while now. Closing it down!
(In reply to Pedro Alves from comment #5) > This has been in place and working great for a while now. Closing it down! Does this mean the bug should be resolved?
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
We dropped the d-3/d-10 variation test for aurora because there couldn't be builds for every day, all the other tests are running.
You need to log in before you can comment on or make changes to this bug.