Sandbox Handbook·2 min read

Scenario 4: order-events-consumer — RCA Rejected

A Kafka lag spike that turns out to be the team's own load test — rejected by a human reviewer as a false positive.

Consumer lag spiked to 42,000 messages overnight. The AI's top hypothesis (under-provisioned consumer) looked plausible, but the pattern actually matched the team's own load-testing harness.

Steps to test

  1. Open INC0000004.
  2. Steps 4–7: kafka_consumer_lag spikes; a log line names the load-test harness right before it.
  3. Steps 10–11: top hypothesis at 0.61 confidence.
  4. Step 12: the reviewer rejected it — the step shows Failed, with the rejection reason recorded.
Outcome: no remediation generated — see how a rejected RCA is displayed differently from an approved one.
Back to Sandbox Handbook overview
← PreviousScenario 3: ehr-patient-records-db — Awaiting ReviewNext →Scenario 5: notification-dispatch-svc — RCA Refined