Closed
Bug 1344234
Opened 8 years ago
Closed 8 years ago
Add hindsight monitor for ping volumes
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gfritzsche, Assigned: trink)
References
(Blocks 1 open bug)
Details
We want:
- email alerts to telemetry-client-dev@mozilla.com
- graphing over time, per-channel, per-type
- regression detection, per-channel, per-type
This should give us timely alerts of any regressions in ping volumes, e.g. when a ping is suddenly sent much more often or stops being sent.
Updated•8 years ago
|
Assignee: nobody → mtrinkala
Points: --- → 2
Priority: -- → P1
| Assignee | ||
Comment 1•8 years ago
|
||
The proposal for the alert configuration follows. However, there are several issues.
volume = {
inactivity_timeout = 5, -- minutes with no data
percent_delta = 10, -- optional
},
Issues:
1) the percent_delta can be based on a model
- The model requires much more setup and since volumes can be highly variable much more maintenance and constant tuning.
2) the percent_delta can be based the same day of the previous week.
- Using the previous week's data is easy but will be noisy. e.g. if there is an anomaly this week (infrastructure deploy) the system will alert now and a week from now.
- the percent_delta can creep up each week so in less than two months the volume could have doubled without an alert
Blocks: 1348863
| Assignee | ||
Comment 3•8 years ago
|
||
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•