{"id":77120,"plugin_id":"plugins_6ab424ad5b448191b8fede2ebf569333","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:27.248Z","digest":"b4facf63072098bf86534a4138ca1f9a0cb69219effb88896e0e71cda425a6d7","against":null,"payload":{"description":"Define data-platform operational telemetry, SLOs, alerting and cost drivers tied to recovery decisions.","included_files":[],"name":"observe-data-platform","skill_md_contents":"---\nname: observe-data-platform\ndescription: Define data-platform operational telemetry, SLOs, alerting and cost drivers tied to recovery decisions.\n---\n\n\n# Operate and observe data platforms\n**Trigger:** Observability, lag, alert fatigue, pipeline SLAs, operational dashboards or cost/reliability trade-offs.\n\n1. Define customer-facing outcomes: dataset freshness, completeness, correctness, availability, recovery time and cost/run.\n2. Instrument per-stage source/target counts, run IDs, offsets, rejects, backlog, state, schema drift, retries, queue time and resource utilization.\n3. Separate detection signals from diagnostic context; alerts need severity, owner, routing and runbook, not vanity charts.\n4. Define SLI and meaningful SLO thresholds, alert evaluation windows, missing-signal policy and recovery verification criteria.\n5. For costs, locate unnecessary full scans, shuffles, extra reprocesses, idle compute and small files **after** correctness is safe.\n6. Provide dashboard outline, alert table, incident links and documented limitations; don't fabricate measured values.\n\nRead `../../references/observability-and-cost.md`, `../../templates/incident-brief.md`.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}