Product Catalog Failure
Failure scenario
This failure occurs when the productCatalogFailure flag is enabled in the Flagd configuration (either through the Kubernetes ConfigMap or the Flagd UI).
When activated, this flag causes GetProduct requests for the specific product ID OLJCESPC7Z to fail with 100% consistency.
Root Cause Analysis by Coroot
How it works
1. Anomaly detection
Coroot's RCA started from an anomaly in errors in the frontend-proxy service. No other input from a user was required, the system automatically detected the issue.
2. eBPF-Based metrics correlation
The first step used eBPF-based metrics to identify the problematic service. It detected errors in the frontend-proxy service, which correlated with issues in the frontend service, then checkout, and finally the product-catalog. This step worked even without OpenTelemetry instrumentation.
3. Traces analysis
The previous step found the failing service but didn't show that the issue was caused by a feature flag. Trace analysis revealed this, and Coroot found the feature flag using tracing attributes.
Results
2/3Successfully identified the product-catalog service as the source of failures
Suggested disabling the feature flag as a precise, actionable solution
The specific product ID was not identified in the analysis
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.