Cart Failure
Failure scenario
The cart service has a feature flag cartFailure enabled that simulates Redis connection failures.
This causes the EmptyCart operation to fail with "Wasn't able to connect to redis" errors.
Root Cause Analysis by Coroot
How it works
1. Anomaly detection
Coroot detected an anomaly in the frontend-proxy service, identifying increased latency and failed requests affecting the checkout flow.
2. eBPF-based metrics correlation
Using eBPF metrics, Coroot traced the latency correlation across the entire request path, identifying the cart service as the bottleneck with EmptyCart operations taking 17+ seconds to fail.
3. Understanding the cause
Coroot identified that the issue stems from a feature flag configuration in the cart service that simulates infrastructure failures for testing purposes. The EmptyCart operations fail with "Wasn't able to connect to redis" errors, causing timeout handling overhead and cascading delays through checkout → frontend → frontend-proxy.
Results
3/3Successfully identified the cart service as the source of Redis connection failures
Recommended disabling the cartFailure feature flag to restore normal cart service operation
The analysis showed how the simulated Redis connection failures created a cascading latency problem throughout the entire checkout experience
LLM Usage Details
Based on $3 per 1M input tokens, $15 per 1M output tokens
Try Coroot's AI RCA in your environment
See how Coroot finds root causes for your real production issues with a full enterprise trial.