new event trigger metric_threshold on "format maison" reports, params: metric key (falls back to the label), operator (>, >=, <, <=), warn and/or fail threshold;
matching enabled rules are applied while the report is processed: a metric's status, and the report's status, become the worst of what the sender declared and what the rules compute — so badges and aggregates reflect it too;
the event fires when the computed level goes up (none → warn, warn → fail, none → fail).
Frontend: argus/frontend#18.

Design retained in the monitoring plan (phase 2.2): - new event trigger `metric_threshold` on "format maison" reports, params: metric `key` (falls back to the label), operator (`>`, `>=`, `<`, `<=`), `warn` and/or `fail` threshold; - matching enabled rules are applied while the report is processed: a metric's status, and the report's status, become the worst of what the sender declared and what the rules compute — so badges and aggregates reflect it too; - the event fires when the computed level goes up (none → warn, warn → fail, none → fail). Frontend: argus/frontend#18.

Gilles referenced this issue

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

Native organizations and external projects #30

Gilles referenced this issue from a pull request that will close it,

2026-10-28 15:34:06 +00:00

Metric threshold rules for custom reports #34

Gilles referenced this issue from a commit

2026-10-28 15:34:06 +00:00

feature: metric threshold rules for custom reports

Gilles referenced this issue from argus/frontend

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

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