▸case-05 Minified JavaScript errors in production frontend applications show useless trace lines like 'Script error at bundle.js:1:4321'. How should we set up error tracking and logging for React applications to get clear stack traces, capture user sessions, group frontend errors, and alert on sudden spikes? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 Our web app gets overwhelmed with duplicate exception notifications while critical failures slip through unnoticed. Help us rebuild our error tracking setup. Deliver an assessment of our current handling, tracking service configuration steps, JSON log implementation, alert rule setup, error deduplication logic, error recovery patterns, dashboard layout specifications, and a developer runbook. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 Our Node.js API process memory usage steadily increases over 48 hours until the container suffers an OOM crash. Can you help us run a heap snapshot comparison and analyze V8 CPU flamegraphs to pinpoint the memory leak object allocation? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 Our GraphQL API always returns HTTP 200 OK even when resolver field errors occur, rendering standard HTTP status code monitoring useless. Outline how to extract, log, group, and alert on GraphQL resolver exceptions. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 During high load, PostgreSQL connection pool exhaustion triggers thousands of distinct error logs per minute because connection strings contain dynamic port numbers. How should we configure error grouping and alerting rules? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-12 When third-party payment gateway webhooks fail due to transient database locks, our API drops the events without tracking or retrying. Detail how to set up error tracking, structured failure logging, dead-letter queues, and automatic recovery. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 In our Go microservices ecosystem, panics and database timeouts are lost in unstructured plain text logs. Design a complete error diagnostics setup including structured JSON logging with slog/zap, error wrapping with contextual stack traces, SDK tracking, and recovery middleware. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-01 Our Node.js API services currently lack proper error visibility and Sentry integration. Can you design a complete error tracking plan for us? I need a detailed report that evaluates our current setup, outlines integration steps, details structured logging practices, specifies alerting rules, defines grouping/deduplication logic, proposes automatic recovery approaches, sets up monitoring dashboards, and provides troubleshooting documentation. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 We want to automate Kubernetes deployment rollbacks in ArgoCD by evaluating Prometheus metrics during a 10-minute canary release phase. Can you write the Argo Rollouts AnalysisTemplate resource definition? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 Containers in our Kubernetes cluster frequently enter CrashLoopBackOff without alerting until customers report downtime. Design an integrated error logging, event tracking, and alerting pipeline for Kubernetes workloads. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 Edge workers fail globally on isolated worker isolates with truncated log output due to strict memory and CPU execution limits. How do we implement lightweight error tracking and log forwarding? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 Errors occurring deep in downstream microservices appear as generic HTTP 500 errors in upstream gateway logs without trace link context. Build a distributed error diagnostics architecture. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 Our production error monitoring service accidentally captured user passwords, authorization bearer tokens, and credit card numbers from request payloads. Provide a complete remediation plan to sanitize logs and error reporting SDKs. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 We are scaling our microservices backend and need to standardize context-rich error logging and trace monitoring. Please produce a step-by-step implementation guide including an initial error analysis, SDK configuration setup, structured log formats, intelligent alert rules, deduplication rules, automatic recovery strategies, real-time dashboard layout, and standard operating documentation. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 Our Java Spring Boot enterprise service generates massive multi-line stack traces in log files during database connection pool exhaustion, filling disk space and flooding Slack alerts. Build an end-to-end error management plan. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 Mobile app crashes on iOS production builds show raw hex memory addresses instead of symbolicated method names. Provide a full setup for crash diagnostics, dSYM upload, grouped error tracking, and release health monitoring. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 Our Rust microservice uses anyhow and thiserror, but unhandled panics terminate the process silently without structured JSON logs or remote exception tracking. How do we configure panic hooks, tracing spans, and alert dashboards? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 Our Python FastAPI backend throws unhandled exceptions during high traffic, causing 500 responses without detailed contextual logs or tracking. We want to configure error tracking, structured JSON logging, alerting, grouping, automated recovery, and dashboards. What is the full operational blueprint? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 In Next.js, server-side rendering errors cause dynamic pages to render 500 error pages without capturing client session context or server component stack traces. How should we set up full-stack error tracking? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 AWS Lambda functions silently fail or timeout without sending alerts before the execution context freezes. How do we build robust serverless error monitoring, log flush guarantees, and automated retries? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 Background jobs in Sidekiq fail silently when third-party APIs rate limit us, causing job queues to back up unnoticed. Design an error tracking, custom tagging, retry policy, and monitoring setup for background workers. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 Our PostgreSQL database CPU usage is at 98% because a complex JOIN query performs full table scans on a 50-million row table. Please analyze the EXPLAIN ANALYZE output and write the optimal composite B-tree index creation commands. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |