Closed Bug 742883 Opened 8 years ago Closed 8 years ago
Verify volume of daily Telemetry ping data
We should have an automated system to verify the volume of daily Telemetry ping data (how many pings are coming in). This system should catch issues like the breakage due to persistent Telemetry seen on Nightly back in Feb 2012. Taras suggested that we can model the uptake of builds on various channels to incorporate variance due to new releases/builds. Can we simplify and track the number of pings per channel and make the assumption that a user on a specific channel will consistently be a user of that channel even if they update to a later build? In this way we can measure absolute volume of pings per channel, which should be easier. We should detect significant drops or increases in pings and raise an automated flag (email to stakeholders?).
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-833
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
As commented on bug 742897, we test ES data for: - existence of aurora data for yesterday and variation d/d-7; - existence of nightly data for yesterday and variation d/d-7; - existence of beta data for yesterday and variation d/d-7; - existence of release data for yesterday and variation d/d-7. so if there is a significant drop or increase we'll get a warning.
This has been in place and working great for a while now. Closing it down!
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Whiteboard: [Telemetry:P1] migrated to JIRA → [JIRA METRICS-833] [Telemetry:P1]
You need to log in before you can comment on or make changes to this bug.