Silent-source (stale) event trigger #29

New issue

Closed

opened 2026-10-28 15:12:49 +00:00 by Gilles · 0 comments

Gilles commented

2026-10-28 15:12:49 +00:00

Owner

Part of the monitoring plan (phase 2.1): get alerted when a source stops reporting (dead man's switch).

Scope

New event trigger stale ("Source muette").
The expected period comes from the report's expect_every (see the JSON/source issue); a rule can override it with its own after parameter. Streams with neither are never considered silent.
A periodic Celery task (every 5 minutes) compares each stream's last reception (max(uploaded_at, last_seen_at) of its latest report) with the expected period plus a tolerance (max(10 min, 10 %)), fires the event on the false → true edge, and raises an info "back" event when the stream reports again.

Part of the monitoring plan (phase 2.1): get alerted when a source stops reporting (dead man's switch). ## Scope - New event trigger `stale` ("Source muette"). - The expected period comes from the report's `expect_every` (see the JSON/source issue); a rule can override it with its own `after` parameter. Streams with neither are never considered silent. - A periodic Celery task (every 5 minutes) compares each stream's last reception (`max(uploaded_at, last_seen_at)` of its latest report) with the expected period plus a tolerance (max(10 min, 10 %)), fires the event on the false → true edge, and raises an info "back" event when the stream reports again.

Gilles added the

feature

label

2026-10-28 15:12:49 +00:00

Gilles referenced this issue from argus/frontend

2026-10-28 15:12:50 +00:00

Rule editor: silent-source and metric-threshold triggers #18

Gilles referenced this issue from guardians_of_the_galaxy/ci-base

2026-10-28 15:12:51 +00:00

Prune jobs: announce expect_every for Argus silent-source alerts #12

Gilles referenced this issue

2026-10-28 15:18:21 +00:00