Silent-source (stale) event trigger #33
No reviewers
Labels
No labels
breaking
bug
ci
dependencies
documentation
feature
security
skip-changelog
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
argus/backend!33
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/29-stale-trigger"
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?
Closes #29
Part of the server monitoring plan (phase 2.1). Stacked on #32 (base
feat/28-sources-json-dedup).Changes
Trigger.STALE("Source muette", default severity alert), in the newPERIODIC_TRIGGERSset (never evaluated on upload).after(validated duration, stored in seconds) or else the stream's latest reportexpect_every. No period → never silent.engine.check_stale(): for each enabled stale rule, the latest DONE report of every matching stream (ref, type, custom name, variant); silent whennow - max(uploaded_at, last_seen_at) > period + max(10 min, 10 %). State tracked inEventRuleState.active: one alert on the edge, then one info event ("de nouveau active") when the stream reports again._raisegained an optionalseverityoverride for that.apps.events.tasks.check_stale_sourcesevery 5 minutes, seeded onpost_migrate(IntervalSchedule).sweep-closed-prs,prune-history) now announceexpect_every: 1d.apps/events/test_stale.py.Checks
pytest (215 passed), pylint 10/10, autopep8, bandit clean.
🤖 Generated with Claude Code
https://claude.ai/code/session_014BSmBtGWeFBD9z4mYm9SjA
📊 Rapports Argus pour cette PR