"The case of a missing item!"
summary
An e‑commerce site shows HTTP 500s when adding items; logs contain 85,000 events for 24 hours, filtered to ~3,000 in the last hour and then 200 failing adds tied to the purchase service. The team uses Loggly/Splunk/ELK for aggregated searches and switches between time‑series (Prometheus/CloudWatch) and logs (Grafana dashboards). A single malformed item_id causes the failures when multiple users add that SKU, so fixing input validation or database schema for that item resolves the error.
AI-written summary · about
related talks
44mPerformance Testing with a "Big Data Tool"
06m“The Power of No”
40mManeuvering Errors within the Bowels of JavaScript
28mProduction Testing Through Monitoring
44mObservability meets a Flaky Test
40mPerformance Testing and Big Data
47mHow to be a Performance Detective?
46mBlink and You’ll Miss It: Stories From Discovering Most Annoying Bugs and Test Flakes