Skip to content
AutoObserve
Design Partner

Demo · Canonical incident

Investigation workspace

Predetermined walkthrough of checkout-latency. Inspect evidence without signing up.

highcheckout-api+340% latency

Checkout latency increased 340%

Checkout p95 latency rose sharply after checkout-api v2.14.7, cascading into payment-service load and an SLO breach.

checkout SLO breached

Root-cause confidence

High

94%

Predetermined demo · no signup required

Timeline

What changed in the window

  1. Deployment

    Deployment checkout-api v2.14.7

  2. Saturation

    DB connection pool saturation begins

  3. Latency

    checkout-api latency increases

  4. Retry

    Retries increase

  5. Dependency

    payment-service load increases

  6. SLO

    Checkout SLO breached

Causal graph

How the failure propagated

deploy v2.14.7connection pool …DB saturationcheckout latencyretriespayment overloadSLO violation

Evidence

Inspect the sources behind the claim

Evidence · Deployment

Deployment

checkout-api:v2.14.7 deployed 8m before incident

Correlationhigh

Evidence · Metric

Metric

p95 latency +184%; connection acquisition timeouts +930%

Correlationhigh

Evidence · Trace

Trace

DB spans +412 ms versus baseline

Correlationhigh

Evidence · Kubernetes

Kubernetes

checkout-api restarted ×3 during the window

Correlationmedium

Evidence · Log

Log

connection acquisition timeout messages spike

Correlationhigh

Evidence · Historical pattern

Historical pattern

Baseline deviation vs prior 7 days of checkout p95

Correlationmedium

Root cause

Explain

Root-cause confidence

High

94%

checkout-api v2.14.7 changed connection pool configuration (100 → 20), causing DB saturation and checkout latency.

  1. 01Deployment v2.14.7
  2. 02Pool size 100 → 20
  3. 03Connection saturation
  4. 04Request queuing
  5. 05Checkout latency
Become a Design PartnerInvestigations docs