signals-scout-insight-alerts

List alerts with alerts-list, then pull firing history with alert-get and check for missing notification_sent_at, empty targets_notified, or notification_suppressed_by_agent. Firings with those markers are the highest-value missed signals to report.

It ranks each firing by missed-ness, materiality, and persistence. A material firing well past its threshold bound that was never notified or is still open and unacted clears the bar; marginal breaches and single flaps do not.

No, it does not re-detect anomalies. It triages the firing history of alerts users already configured, since the team chose the thresholds themselves; anomaly scoring of viewed insights belongs to a separate sibling scout.

A persistent breach stays a single report. The scout edits the existing report with append_note containing the fresh firing's calculated value, fired-at time, and notification status instead of filing a duplicate.

Snoozed or disabled alerts, flapping alerts that fire and resolve within one interval, already-notified-and-resolved firings, marginal breaches on noisy series, dev or test environment alerts, and transient single-check errors are all skipped.

At most about five reports per run, ranked worst-first by the triage discriminator. If more findings clear the bar, the close-out summary states how many were dropped rather than silently truncating them.