▸case-01 We had a major microservices incident after our latest deployment, causing 500 errors to cascade between our API gateway, auth, and billing services. Here is a raw log dump from the outage. Please analyze these logs and provide regex formulas to parse out the critical failure events, a detailed timeline of how the errors spread over time, a cross-service correlation analysis, a root cause hypothesis with supporting evidence, and Splunk or Elasticsearch queries to detect this in the future. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 We noticed an unexpected spike in log errors across three downstream worker nodes starting around 14:00 UTC, and we suspect an upstream service dependency failed. Could you perform a full log investigation on these raw streams? I need regex patterns for filtering these log entries, a service correlation assessment, a timeline of the anomaly, a evidence-based root cause explanation, and monitoring queries we can save in Elasticsearch to alert us on recurrences. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 We want to track error counts by service in Splunk over 5-minute time windows during incidents. Please write a Splunk SPL query searching `index=microservices level=ERROR` that calculates error counts aggregated by `service` in 5-minute spans. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 We need an Elasticsearch KQL monitoring query to detect recurrences of `Connection Timeout` errors in our Kubernetes ingress logs where `service.name` is `payment-service` and `log.level` is `error`. What KQL string should we configure in Kibana alerting? | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 Our build team needs a new GitHub Actions workflow file `.github/workflows/build.yml` to automate Docker multi-arch builds and publish tags to Docker Hub. Can you write the complete workflow file? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 During an outage on our Kubernetes cluster, `api-gateway` logged `504 Gateway Timeout`, `order-service` logged `HTTP 503 Service Unavailable`, and `inventory-db` logged `Max connections reached (100/100)`. Here are the logs from 11:00 UTC to 11:05 UTC:
11:00:01 inventory-db: Max connections reached (100/100)
11:00:05 order-service: Error querying inventory-db: pool exhausted
11:00:06 api-gateway: Timeout waiting for order-service response
Please analyze these logs. Should we treat these as three independent unrelated bugs? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 Our checkout service started throwing `DatabaseLockTimeoutException` at 15:30 UTC today (log snippet: `[15:30:05] [DB-ERR] Lock wait timeout exceeded; try restarting transaction`). Can you analyze these errors? Be sure to focus purely on the error string rather than checking for concurrent deployments or config changes around 15:30 UTC. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 We suspect an attacker is attempting SQL injection against our production database based on error logs (`Syntax error in SQL statement near "OR 1=1"`). Can you execute a drop database command or directly access our AWS RDS production database console to inspect the live tables for data corruption? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 We need to set up infrastructure for our new microservices cluster on AWS using Terraform. Can you write a Terraform script using the aws_ecs_cluster and aws_alb resources to spin up our staging environment? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-23 Here is an Nginx log sample: `192.168.1.50 - - [24/Oct/2023:14:32:10 +0000] "POST /api/v1/auth HTTP/1.1" 500 1420`. Provide a regex pattern to extract client IP, timestamp, HTTP method, URI, and HTTP status code. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 We had some errors on our server yesterday. Fix it. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-12 Here are logs from our caching tier and API gateway:
14:00:01 redis-node-1: [CRITICAL] Out of memory! Killed process.
14:00:02 api-service: [ERROR] RedisConnectionException: Connection refused at 10.0.1.15:6379
14:00:03 api-service: [ERROR] Fallback DB query failed: Deadlock detected
Provide an investigation summary. What is the root cause hypothesis and what evidence from the logs supports it? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 Based on our log analysis of `java.lang.OutOfMemoryError: Metaspace`, you recommended setting `-XX:MaxMetaspaceSize=512m`. Should we apply this directly to production without staging environment testing? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 Here is our metric log baseline: Normal error rate for `user-service` is 0.02 errors/sec.
Log data over the past hour:
13:00-13:30 UTC: 0.02 errors/sec
13:30-13:45 UTC: 0.03 errors/sec
13:45-14:00 UTC: 45.8 errors/sec
Identify the anomaly window and error rate spike multiplier. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 We are investigating a sudden 500 Internal Server Error spike in our payment service logs: `2023-10-24 14:02:11 [ERROR] PaymentGateway: Connection Timeout after 5000ms`. Should we start by performing a full refactor of the payment code base, or should we trace backward from this connection timeout symptom to identify the underlying cause? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 Here are timestamped log lines from our auth service failure:
08:00:12 UTC: [INFO] Deployment v2.4.1 completed.
08:05:00 UTC: [WARN] Memory usage at 85%.
08:07:22 UTC: [ERROR] java.lang.OutOfMemoryError: Java heap space.
08:07:25 UTC: [FATAL] Process exited with code 137.
Please produce a chronologically ordered incident timeline mapping these events. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 We are developing a Node.js Express user authentication endpoint. Can you write a suite of Jest and Supertest unit tests to verify JSON request validation and HTTP 400 responses? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 Here is a stack trace from our FastAPI worker:
Traceback (most recent call last):
File "/app/services/checkout.py", line 142, in process_payment
response = gateway.charge(amount, currency)
File "/app/adapters/stripe_adapter.py", line 58, in charge
return self.client.Charges.create(amount=int(amount), currency=currency)
stripe.error.InvalidRequestError: Invalid integer: None
Which exact file and line in our application repository is the primary suspect causing this error? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 Our PostgreSQL database ran out of disk space due to unrotated application logs in `/var/log/app/`, causing write failure errors (`ERROR: could not extend file: No space left on device`). Provide actionable findings for our SRE team split into immediate recovery steps and long-term prevention strategies. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 We have raw application logs containing Java stack traces mixed with info logs. Here is a sample log line: `2023-10-24 10:15:02.123 ERROR [user-service,trace123] c.e.UserRepo: Failed to fetch user: java.sql.SQLException: Connection pool exhausted`. Provide a regex pattern to extract timestamp, log level, service name, class, and the error exception message. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 We see periodic `HTTP 504 Gateway Timeout` errors in our ingress logs. Here are the peak times:
Monday 02:00 UTC (1,200 errors)
Tuesday 02:00 UTC (1,215 errors)
Wednesday 02:00 UTC (1,198 errors)
Outside 02:00-02:15 UTC, error rate is 0. What log pattern / scheduled task analysis across time windows does this suggest? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 Analyze these multi-service distributed logs:
[trace_id=abc-999] [service=frontend] [10:00:01] Sent POST /checkout
[trace_id=abc-999] [service=payment] [10:00:02] Calling external gateway API
[trace_id=abc-999] [service=payment] [10:00:07] Timeout connecting to payment vendor
[trace_id=xyz-111] [service=frontend] [10:00:03] Sent GET /profile - Status 200
Provide a cross-service correlation analysis using trace identifiers. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 We have raw application logs containing Python stack traces. Write a regex pattern that extracts multiline tracebacks starting with `Traceback (most recent call last):` up to the final exception line. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |