observability-auditlisted

# Observability Audit <!-- anthril-output-directive --> > **Output path directive (canonical — overrides in-body references).** > All file outputs from this skill MUST be written under `.anthril/audits/observability-audit/`. > Run `mkdir -p .anthril/audits/observability-audit` before the first `Write` call. > Primary artefact: `.anthril/audits/observability-audit/<artefact>`. > Do NOT write to the project root or to bare filenames at cwd. > Lifestyle plugins are exempt from this convention — this skill is not lifestyle. ## When to use Run this skill when the user mentions: - Observability audit, logging review - Metrics coverage, tracing coverage, alert quality, dashboard review - OpenTelemetry, Prometheus, Grafana, Datadog, New Relic Scores four pillars 0”“5: logs (structured, correlation IDs, PII scrubbing, level discipline), metrics (RED/USE coverage, cardinality discipline, histogram buckets), traces (service-boundary spans, attribute conventions, sampling), and alerts/dashboards (paging vs non-paging, runbook links, symptom-based alerts, golden-signal dashboards, SLO burn-rate panels). Cross-cutting — does not spawn parallel sub-agents. ## Before You Start 1. **Determine operating mode.** `--live` requires Prometheus / Grafana / OTel / Datadog endpoint config and read-only API keys via env (`PROM_URL`, `GRAFANA_URL`, `GRAFANA_API_KEY`, `DD_API_KEY`). `--runtime` fires a synthetic alert — **non-prod only unless `--i-really-mean-prod`**. 2. **Find observability surfa