Proactive stale/failing product admin alerting #8
Labels
No labels
area:ai
area:ci-cd
area:notifications
area:observability
area:public-pages
backlog
bug
duplicate
enhancement
help wanted
invalid
question
type:decision
type:feature
type:infra
type:maintenance
type:security
v1.0.1
v1.1.0
v1.2.0
v1.3.0
v2.0.0
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/WeatherBot#8
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Target release: v1.1.0
Freshness historical samples, 24-hour counters, and cache hit/miss rates already exist. Add the remaining proactive piece.
Acceptance
Source:
docs/ROADMAP.md→ Planned → Product Freshness Metrics and Alerting.Done in #96 (merged). A scheduler job (
stale_product_alert_job) evaluates the critical feeds (nws_alerts,spc_fetch) and notifies admins when one stays stale (last success older thanSTALE_PRODUCT_ALERT_MINUTES) or failing, debounced on state transitions so it doesn't spam. Delivery is via the shared admin-alert helper (ADMIN_ALERT_WEBHOOKif set, else logged). With #73's/metricsalso in place, an external Alertmanager can drive this too — the in-app job is the self-contained default.