fix(alerts): the slow-burn ticket can reach its own threshold - #375
Merged
Conversation
queue_wait_slow_burn asked for a queued wait above 600 s held for fifteen minutes. Measured against a full day of the metric -- 2026-09-02, with one project's dispatched release CI bursting the priority pools and jobs waiting up to 906 s -- that would have fired zero times on every scale set. The queued wait does not stay above ten minutes for a quarter of an hour: the provider assigns the intent first and the rest of the wait belongs to lifecycle_assigned_stall. The rule also contradicted its own summary, which places it "between the two-minute objective and the five-minute page". A ticket must hold at least ten minutes -- the package's own policy for the class -- so the threshold comes down to where a ten-minute hold can reach: 300 s, the five-minute mark the summary names. On that same day it fires once. The measured grid is in the rule's comment so the next person can re-derive it rather than trust it. Claude-Session: https://claude.ai/code/session_0128syXKxAGCfJGRDxUUNQXp
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
queue_wait_slow_burnasked for a queued wait above 600 s held for fifteen minutes. Measured against a full day of the real metric (2026-09-02, one project's dispatched release CI bursting the priority pools, jobs waiting up to 906 s): zero episodes on every scale set. The queued wait does not stay above ten minutes for a quarter of an hour, because the provider assigns the intent first and the remainder of the wait belongs tolifecycle_assigned_stall. The rule also contradicted its own summary, which places it "between the two-minute objective and the five-minute page".Episodes on that day by (threshold, minutes held): (300, 5) = 18, (300, 10) = 1, (420, 5) = 4, (450, 5) = 3, (540, 5) = 2, (600, 5) = 0, and zero for anything held fifteen minutes.
A ticket must hold at least ten minutes — the rule package's own policy for the class, and the right one — so the threshold comes down to where a ten-minute hold can reach: 300 s, the five-minute mark the summary already names. It fires once on that day. The grid is in the rule's comment so the next person can re-derive it instead of trusting it.
https://claude.ai/code/session_0128syXKxAGCfJGRDxUUNQXp