← Aivana Database EngineerCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Aivana Database Engineer
Snapshot Sep 30, 2026 · 23:16 UTC · version 1.1.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"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"
}SHA-256: ea6e169c9fbe12e5607175c9a6a21ad8aaeffa91a31acc3e03fce3cd38f9ecdf