Domain-specific extensions to the Crisis Response Chain and TRACE / DEBUG mnemonics for database, query, and data-platform incidents.
Placeholder for database and data-platform content (queries, connections, replication, storage). TRACE, DEBUG, STOP→TRACE→DEBUG→8D apply broadly; add workflows that fit your stack.
Add pipelines, checklists, or mnemonic adaptations for:
- Query performance — slow queries, execution plans, indexes, statistics; where DEBUG’s “Understand data flow” meets the DB
- Connections / pooling — exhaustion, timeouts, connection limits; handoff from TRACE/DEBUG
- Replication / HA — lag, split-brain, failover; integration with 8D D3 (containment) and D4 (RCA)
- Storage / I/O — disk, IOPS, growth; when to branch from TRACE “Review logs and metrics”
- Schema / migrations — lock contention, DDL, version drift; links to 8D and ICEBERG for recurring issues
Keep the same structure as the main guide: when-to-use, steps, pitfalls, “combines well with,” real-world example. Link back to TRACE, DEBUG, 8D, ICEBERG, and METRICS.
- PR adding a
###section under a placeholder (or propose a new one). - Reuse existing mnemonics where possible.
- CONTRIBUTING · FIELD-REPORTS