observability

DE//AGENT currently lists 7 resources under observability: 6 tutorials, 1 hook. 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
• Separate infrastructure metrics from data signals — freshness, volume, schema, distribution — via Hold the observability mental model: infrastructure metrics versus data signals
• Place lineage and the catalog on the observability map, next to metrics and traces — via Hold the observability mental model: infrastructure metrics versus data signals
• State what each layer answers and which tool owns it — via Hold the observability mental model: infrastructure metrics versus data signals
• Assemble the full stack — metrics, alerts, traces, lineage, catalog — via Capstone: the data-platform observability checklist
• Gate schedule and column changes pre-merge with SLA and impact checks — via Capstone: the data-platform observability checklist

10 more objectives live on the individual resource pages.

These resources map to stage: Observability (7). 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. Hold the observability mental model: infrastructure metrics versus data signals score 34.15 — beginner
3. Capstone: the data-platform observability checklist score 34.15 — intermediate

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, Hold the observability mental model: infrastructure metrics versus data signals.

Security-flagged entries: Incident drill: a broken upstream caught by freshness and lineage (2 flags), Production gotchas: alert fatigue, missing contracts, no-data silence (2 flags), Freshness Pre-Merge Check (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
• Hold the observability mental model: infrastructure metrics versus data signals — Two layers live on one data platform: infrastructure metrics (CPU, lag, job success) and data signals (freshness, volume, schema, distribution). This lesson separates them, places … details
• Capstone: the data-platform observability checklist — Ten lessons compress into one page. Declare SLAs, express them as metrics and alerts with explicit no-data handling, instrument runs with traces, emit lineage events, keep the cata… details
• Instrument pipelines with OpenTelemetry: traces for data jobs — Traces give every pipeline run a story — which task ran, how long, with what attributes. Wrap a job with OpenTelemetry, adopt the semantic conventions so attribute names match acro… details

Adjacent topics: tutorial (6 shared), sla (3 shared), freshness (3 shared), production (2 shared), prometheus (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.