Closed
Bug 1312863
Opened 9 years ago
Closed 6 years ago
consider adding support for monitoring crash stats with scheduled changes
Categories
(Release Engineering Graveyard :: Applications: Balrog (backend), defect, P3)
Release Engineering Graveyard
Applications: Balrog (backend)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bhearsum, Unassigned)
Details
(Whiteboard: [lang=python])
We added support for Scheduled Changes in Balrog awhile back. It was originally designed with the idea of monitoring Telemetry for uptake, and automatically making changes to Rules based on a certain amount of uptake (eg: to shut off after we hit target uptake of a throttled rollout).
Something that may be nice to do is add similar integration with crash-stats - and have a way to automatically shut off updates if a particular product and/or channel and/or platform gets a big crash spike.
I haven't spoken with anyone on the crash stats side, but I just want to get it on file for now as an idea.
Reporter | ||
Updated•8 years ago
|
Priority: -- → P3
Whiteboard: [lang=python]
Reporter | ||
Comment 1•6 years ago
|
||
This has never come up us something we want to do.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•