alerting

DE//AGENT currently lists 3 resources under alerting: 2 tutorials, 1 reference. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Documented learning objectives across these resources:

• Declare a freshness SLA and compute worst-case lag from a schedule — via Express a freshness check as a metric and an alert
• Express staleness as a metric and write an alerting rule — via Express a freshness check as a metric and an alert
• Configure no-data handling so silence is an alert, not a pass — via Express a freshness check as a metric and an alert
• Tie every alert to a declared SLA so paging has a contract — via Production gotchas: alert fatigue, missing contracts, no-data silence
• Configure no-data handling and evaluation intervals explicitly — via Production gotchas: alert fatigue, missing contracts, no-data silence
• Catch schedule-vs-SLA drift at pre-merge instead of at 3 a.m. — via Production gotchas: alert fatigue, missing contracts, no-data silence

These resources map to stage: Observability (3). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

How scores are computed: source quality score.

Highest composite score first:

1. Express a freshness check as a metric and an alert score 34.15 — beginner
2. Production gotchas: alert fatigue, missing contracts, no-data silence score 31.15 — intermediate
3. Grafana Documentation score 27.7 — difficulty not documented

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

Start here if you're new: Express a freshness check as a metric and an alert.

Security-flagged entries: Production gotchas: alert fatigue, missing contracts, no-data silence (2 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

• Express a freshness check as a metric and an alert — The first hands-on of the series: declare a freshness SLA, express staleness as a metric, and write an alert rule — including what happens when no data arrives at all. Ends with th… details
• Production gotchas: alert fatigue, missing contracts, no-data silence — Three failure modes of a monitoring stack that looks healthy: alerts that page until nobody reads them, metrics with no declared SLA behind them, and no-data windows that pass as h… details
• Grafana Documentation — Grafana's official documentation: dashboards, panel queries, alerting (including the unified alerting model), and provisioning. The standard surface where pipeline freshness, volum… details

Adjacent topics: tutorial (2 shared), sla (2 shared), observability (2 shared), grafana (2 shared).

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.