fix(alerts): the update ticket waits for the host's own automation - #380
Merged
Merged
Conversation
host_standard_updates_available fired the moment any package appeared. unattended-upgrades runs daily on every fleet host with the Ubuntu archive and -security as allowed origins, so a security update announced in the afternoon is gone by the next morning without anyone reading a ticket. And Ubuntu phases updates per machine, so one set of nine packages reached the five hosts on different days: on 2026-09-02 the rule ticketed four times for that single set, once per host as its phase arrived. The expression now asks whether the count stayed above zero through a full automation cycle -- twenty-six hours, the daily apt timer plus its randomised delay. A package the automation will never take, one from noble-updates rather than -security or a phased deferral, still surfaces a day later, which is when it stops being the machine's problem. Claude-Session: https://claude.ai/code/session_0128syXKxAGCfJGRDxUUNQXp
rldyourmnd
enabled auto-merge
September 2, 2026 16:54
rldyourmnd
deleted the
fix/the-update-ticket-waits-for-the-automation
branch
September 2, 2026 16:56
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.
host_standard_updates_availablefired the moment any package appeared. Two things make that noise rather than signal:unattended-upgradesruns daily on every fleet host, with the Ubuntu archive and-securityas allowed origins, so a security update announced in the afternoon is gone by the next morning without anyone reading a ticket.The expression now asks whether the count stayed above zero through a full automation cycle:
min_over_time(...[26h:10m]) > 0, twenty-six hours being the daily apt timer plus its randomised delay. A package the automation will never take — one fromnoble-updatesrather than-security, or a phased deferral — still surfaces a day later, which is when it stops being the machine's problem and becomes a person's.Verified against live data: the new expression evaluates cleanly and returns one series per host.
https://claude.ai/code/session_0128syXKxAGCfJGRDxUUNQXp