KPI-46 email leg: mail Elazar on every finding / escalation
Canceled high
bvbin-venus-cc
Add an email leg to kpi-burn-alert.sh: same finding text as the hub DM, sent to Elazar's address on every stage-2 escalation (KPI-47) and on every KPI-46 finding. Reuse the fleet's existing outbound-mail path (rkhunter-scan.sh / scrp-kpiweekly-whey already send mail - copy that mechanism, fix nothing else). Delivery failure must exit non-zero (same rule as the bearer check, v1.17), never warn-and-continue.
Activity
-
parent=#3065
-
parent=KPI-46
-
Elazar 2026-09-03: email to elazar.pimentel@pensanta.com only (5b).
-
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