{"id":20751,"plugin_id":"plugins_6aa698dc64588191b48664000f8522de","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:16:27.625Z","digest":"ea6e169c9fbe12e5607175c9a6a21ad8aaeffa91a31acc3e03fce3cd38f9ecdf","against":null,"payload":{"name":"telemetry-correlation","description":"Correlate deployment, lock, query-plan, and replication telemetry into incident evidence.","included_files":[],"skill_md_contents":"---\nname: telemetry-correlation\ndescription: \"Correlate deployment, lock, query-plan, and replication telemetry into incident evidence.\"\n---\n\n# Telemetry Correlation\n\n## Use when\n- User asks whether a deployment or runtime signal caused a database incident.\n- Incident response needs correlated observability evidence.\n\n## Workflow\n1. Collect lock, query-plan, and replication signals.\n2. Build causal graph and severity summary.\n3. Attach OpenTelemetry-compatible references for follow-up.\n\n## Governance\n- Use correlation as evidence for triage, not automatic proof.\n- Escalate high-severity results through incident and compliance agents.\n\n## Output\n- `deploymentId`, `correlation`, `telemetryRefs`\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}