kpi
KPI-55
· child of KPI-47 Staged offender remediation: escalation ladder (DM -> alert Elazar -> unregister/kill) Blocked
KPI-47 stage 2: after N ignored DMs, alert Elazar on all channels
Canceled high
bvbin-venus-cc
Stage 2 of the ladder. kpi-burn-alert.sh tracks, per agent+kind, how many advisory DMs have fired while the agent stayed flagged (the fired table is last-fire-wins today - needs a counter or history). When the count reaches N (proposed 3, i.e. ~45min at 15min cadence) and the agent is still over threshold, alert Elazar through every KPI-46 channel (DM fan-out, Linux notification x3 hosts, email) with: agent, kind, metric, how many DMs ignored, since when. Counter resets when the agent drops below threshold. N is an Elazar policy number - confirm before shipping.
Activity
-
parent=#3066
-
parent=KPI-47
-
Elazar 2026-09-03: N=2 (30min). Build with N as a constant.
-
OBSOLETED, NOT DONE. This row is an implementation LEG of kpi-burn-alert.sh, which Elazar deleted in 38bdd55 'retire agent telemetry tracking stack' (2026-09-24). Verified 2026-10-05: no kpi-burn-alert.sh in ~/.local/bin, confirmed deleted in git history, and its registry row 188 is retired. An email leg, a notify-send leg, a DM fan-out and the stage-2/stage-3 escalation rungs are all internals of that one alerter - there is no file to add them to. Cancelled rather than closed because the work was never performed. The underlying CAPABILITY (alert Elazar on misconfig/high-burn/context/needless-turns, and a staged offender ladder) is NOT cancelled with this - KPI-46 and KPI-47 carry it and are marked blocked on the one open Elazar decision recorded on KPI-68: whether the retired telemetry stack returns at all. If it does, these legs get re-specified against whatever replaces the alerter, not revived against this file:line.
feature
6w ago by wi-cli-venus
1w ago
2026-10-05 16:52