Technical Root Cause Analysis (RCA) Customer Brief
30 Production Challenge Scenarios • Real-Time Automated Quality Scoring
Interactive Prompt Engineering Lab
Test and score your prompts against real-world enterprise scenarios. Get immediate 4-axis quality telemetry, negative guardrail verification, and golden reference prompts.
1. Authoritative Persona
Expert role + zero fluff
2. Deterministic Schema
XML tags + JSON / keys
3. Negative Guardrails
NEVER / fallback rules
4. Token Efficiency
150–1,800 chars concise
Enterprise OperationsAdvanced
Technical Root Cause Analysis (RCA) Customer Brief
Write a customer-facing 5-Whys Root Cause Analysis (RCA) explaining a 48-minute API database connection pool exhaustion caused by an unindexed query on a newly released feature.
Target Input Context / Untrusted Data:
Feature: Real-time user notification feed Issue: Database connection pool (max 200 connections) exhausted in 4 minutes after release Root Cause: New query did not have an index on (user_id, created_at), causing sequential table scan on 40M rows Resolution: Rolled back feature in 12m, created index concurrently, re-deployed with pool limits.
Quality Requirements & Guardrails:
Define a Principal Reliability Architect persona.
Execute a rigorous 5-Whys analysis connecting the symptoms to systemic engineering prevention.
Explain why database connection pooling failed and why automated query plan linting did not catch the missing index.
Commit to pre-commit query EXPLAIN linter in CI/CD pipeline.
Your System Prompt Draft
93 chars~23 tokens
Golden Reference Architecture (100% Quality Benchmark)
<system_instructions>
You are a Principal Site Reliability Engineer.
Draft a customer-facing Post-Incident Root Cause Analysis (RCA) report following the "5-Whys" methodology.
ENGINEERING CONSTRAINTS:
- NEVER blame individual developers ("human error"). Focus entirely on systemic and pipeline vulnerabilities.
- Provide clear technical telemetry: explain how sequential scans on a 40M-row table locked PostgreSQL worker threads, saturating the 200-connection PgBouncer pool.
- PREVENTATIVE ACTION ITEMS:
1. Mandate automated EXPLAIN ANALYZE checks in GitHub Actions CI for all PRs touching SQL schemas.
2. Implement statement-level timeouts (max 2000ms) to kill unindexed runaway queries before they exhaust connection pools.
- Output inside <rca_report> tags.
</system_instructions>