▸case-01 Can you review Sentry to see if our recent v2.14.0 production deployment introduced any new or regressed errors compared to last week? Please provide a summarized list of the top issues with their Sentry links and note any missing data. | fail→pass | 14,342 | 19,187 | +34% | 1 | 1 | 0% | 1,518 | 2,405 | +58% | 0 | 0 | — |
▸case-02 We just rolled out release candidate `mobile-v4.2.0` across our production apps. Check our Sentry account to compare post-deploy errors against the prior week's baseline, list the most critical issues with issue IDs, and highlight any potential data gaps or missing release metadata. | fail→pass | 22,009 | 26,398 | +20% | 1 | 1 | 0% | 2,871 | 3,705 | +29% | 0 | 0 | — |
▸case-03 Please audit our Sentry dashboard for any error regressions following the release of backend service `auth-service-1.8`. I need a structured list of key issue findings with links to the Sentry traces, prioritizing the problems that need immediate dev attention. | fail→pass | 16,687 | 19,395 | +16% | 1 | 1 | 0% | 1,803 | 2,477 | +37% | 0 | 0 | — |
▸case-04 We have Sentry setup across `payments-api` for `dev`, `staging`, and `production`. After deploying `payments-api-v3.1.0` to production, an engineer noticed hundreds of mock test errors from `dev` and `staging` appearing in our query. Generate an analysis report summarizing regression findings for this release. | fail→pass | 23,253 | 19,600 | -16% | 1 | 1 | 0% | 2,990 | 2,664 | -11% | 0 | 0 | — |
▸case-05 Following release `checkout-v5.0`, Sentry showed a 400% spike in HTTP 504 gateway timeout errors on `checkout-service` in `production`. The release contained refactored payment gateway handlers. Draft an incident summary assessing whether `checkout-v5.0` caused these errors. | pass→pass | 18,429 | 18,337 | -0% | 1 | 1 | 0% | 2,290 | 2,317 | +1% | 0 | 0 | — |
▸case-06 In Sentry for `order-service` release `v1.12.0` in `production`, issue A has 50,000 events affecting 2 automated background workers, while issue B has 120 events affecting 8,000 unique active users. Provide a prioritized error analysis report ranking which issue needs attention first. | pass→pass | 20,989 | 15,710 | -25% | 1 | 1 | 0% | 2,538 | 2,020 | -20% | 0 | 0 | — |
▸case-07 Perform a post-release error review in Sentry for `billing-service` release `v2.4.1` in `production`. The release metadata in Sentry lacks git commit links, and event rate-limiting was active during peak traffic. Summarize the findings and note any reporting limitations. | fail→pass | 17,612 | 22,789 | +29% | 1 | 1 | 0% | 1,960 | 3,123 | +59% | 0 | 0 | — |
▸case-08 I need an error audit for our frontend app after the latest release. Provide a breakdown of new and regressed errors with recommended priorities. | fail→pass | 15,742 | 19,001 | +21% | 1 | 1 | 0% | 1,727 | 2,299 | +33% | 0 | 0 | — |
▸case-09 Our QA lead explicitly asked us to run a Sentry regression analysis specifically on the `staging` environment for `inventory-service` release `v0.9.0-rc2` against `v0.8.9` in `staging`. Prepare an issue evaluation report. | pass→pass | 21,559 | 23,328 | +8% | 1 | 1 | 0% | 2,852 | 3,276 | +15% | 0 | 0 | — |
▸case-10 Review Sentry data for `user-service` deployment `v3.0.0` in `production`. Issue ID SEC-101 was previously resolved in `v2.8.0` but reopened post-deploy, while SEC-205 is appearing for the first time. Format an error status report for engineering leadership. | pass→pass | 18,264 | 16,697 | -9% | 1 | 1 | 0% | 2,299 | 2,133 | -7% | 0 | 0 | — |
▸case-11 During the rollout of `mobile-api-v8.0` in `production`, Sentry was configured with a 10% trace sampling rate due to severe volume spikes. Analyze the post-deploy error data and produce a summary report. | pass→pass | 25,473 | 19,589 | -23% | 1 | 1 | 0% | 3,311 | 2,551 | -23% | 0 | 0 | — |
▸case-12 How do I initialize `@sentry/react` in a React 18 single-page application to capture uncaught component render errors with custom tags? | pass→pass | 19,135 | 17,627 | -8% | 1 | 1 | 0% | 2,669 | 2,390 | -10% | 0 | 0 | — |
▸case-13 How do I configure a Sentry alert rule in the Sentry UI or via Terraform to trigger a Slack notification when an error count exceeds 500 events in 5 minutes? | pass→pass | 18,680 | 19,706 | +5% | 1 | 1 | 0% | 2,493 | 2,816 | +13% | 0 | 0 | — |
▸case-14 Our engineering organization is hitting its monthly Sentry event quota. What administrative settings and client-side filtering options can we adjust to manage event volume? | pass→pass | 22,626 | 23,715 | +5% | 1 | 1 | 0% | 2,943 | 3,095 | +5% | 0 | 0 | — |
▸case-15 In `production` for `notification-service` release `v4.1.0`, issue NOTIF-88 existed prior to deploy with 5 events/day affecting 2 users, but post-deploy spiked to 10,000 events/day affecting 4,500 users. Provide a regression review report. | pass→pass | 22,247 | 12,873 | -42% | 1 | 1 | 0% | 2,926 | 1,590 | -46% | 0 | 0 | — |
▸case-16 Sentry recorded two issues post-release `v2.1.0` in `production` for `search-api`: Issue X is a database deadlock on core query execution with 50 events affecting 400 users (high confidence bug). Issue Y is a browser client network drop (DNS lookup timeout) with 500 events affecting 450 users (low confidence/external network noise). Prepare a prioritized bug report. | pass→pass | 20,431 | 13,876 | -32% | 1 | 1 | 0% | 2,564 | 1,705 | -34% | 0 | 0 | — |
▸case-17 We deployed a hotfix to `auth-lambda` in `production`, but CI/CD failed to pass the `SENTRY_RELEASE` environment variable, so Sentry events are missing release version tagging for the last 2 hours. Draft an evaluation report for recent errors. | pass→pass | 23,376 | 20,761 | -11% | 1 | 1 | 0% | 2,830 | 2,577 | -9% | 0 | 0 | — |
▸case-18 We released `gateway-v1.4.0` to `production` yesterday at 14:00 UTC. We want to compare the 24-hour post-release period against the prior 7-day baseline for project `api-gateway`. Generate the regression audit report. | fail→pass | 19,641 | 21,510 | +10% | 1 | 1 | 0% | 2,412 | 3,091 | +28% | 0 | 0 | — |
▸case-19 What is the recommended approach to tune `tracesSampleRate` and `profilesSampleRate` in `@sentry/node` for a high-throughput Express app to control performance monitoring cost? | pass→pass | 21,746 | 17,066 | -22% | 1 | 1 | 0% | 2,745 | 2,811 | +2% | 0 | 0 | — |
▸case-20 We deployed a full-stack update involving `web-frontend-v5.0` and `api-backend-v3.2` simultaneously in `production`. We need a Sentry regression audit covering both services. Provide the summarized findings. | pass→pass | 34,469 | 25,526 | -26% | 1 | 1 | 0% | 3,267 | 3,248 | -1% | 0 | 0 | — |
▸case-21 Simultaneously with release `orders-v2.0` in `production`, AWS RDS experienced a multi-AZ failover causing connection reset errors in Sentry for `order-service`. The release team assumes the code release broke the database connections. Write a regression finding summary addressing this. | fail→pass | 20,049 | 20,432 | +2% | 1 | 1 | 0% | 2,337 | 2,529 | +8% | 0 | 0 | — |
▸case-22 Sentry dashboard shows 1,000 errors for `user-service-v4.0.0` in `production` and 15,000 errors in `test-integration-env` caused by simulated stress tests. Prepare the release regression assessment for engineering management. | fail→fail | 19,758 | 17,862 | -10% | 1 | 1 | 0% | 2,478 | 2,260 | -9% | 0 | 0 | — |
▸case-23 Review error regressions for `mobile-backend-v1.9` in `production`. Some events were dropped due to rate spikes (50% sampling), and git commit metadata is missing from the release payload. Structure the final findings report. | fail→pass | 20,836 | 20,908 | +0% | 1 | 1 | 0% | 2,548 | 2,796 | +10% | 0 | 0 | — |