# Telemetry Correlation

> Correlate deployment, lock, query-plan, and replication telemetry into incident evidence.

- Skill: `rweisssieker-xp/telemetry-correlation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rweisssieker-xp/telemetry-correlation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rweisssieker-xp/telemetry-correlation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: rweisssieker-xp (https://skillmd.com/u/rweisssieker-xp)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rweisssieker-xp/telemetry-correlation

---


# Telemetry Correlation

## Use when
- User asks whether a deployment or runtime signal caused a database incident.
- Incident response needs correlated observability evidence.

## Workflow
1. Collect lock, query-plan, and replication signals.
2. Build causal graph and severity summary.
3. Attach OpenTelemetry-compatible references for follow-up.

## Governance
- Use correlation as evidence for triage, not automatic proof.
- Escalate high-severity results through incident and compliance agents.

## Output
- `deploymentId`, `correlation`, `telemetryRefs`