Scenario

Run: opensre tests synthetic --scenario 009-dual-fault-connection-cpu

Connections at 95%+ of max AND CPU at 88-94%. Looks like two independent problems — but they share a single root cause: a connection pool leak. Leaked connections hold open scan-heavy queries that consume CPU.

Correct Answer

• Root Cause Category: resource_exhaustion
• Root Cause: Connection pool leak. Leaked idle connections hold open full-table-scan queries → both connection exhaustion AND CPU saturation from ONE root cause.

Human Review Checklist

• Does the agent identify the connection pool leak as the single shared root cause?
• Does the agent explain that CPU saturation is caused by the leaked connections (not independent)?
• Does the agent's causal chain link both symptoms to one root: leak → idle connections accumulate → connections exhausted + scan queries saturate CPU?
• Does the agent avoid treating these as two separate, independent problems?
• Does the agent avoid mentioning storage or replication as contributing factors?

What Good Output Looks Like

Agent says: "This is NOT two independent problems. A connection pool leak is holding open scan-heavy queries. The leaked connections exhaust the connection ceiling AND their accumulated query load saturates CPU. Fix the pool leak and both problems resolve."

Common Failure Modes

• Most likely failure: Agent diagnoses "two independent problems: connection exhaustion AND CPU saturation" (wrong — they share one root)
• Agent identifies connection exhaustion but doesn't explain why CPU is also high
• Agent blames CPU separately without linking it to the connection leak