Your Python service on Cloud Run throws exceptions that nobody notices. You want the stack traces grouped into distinct issues with occurrence counts, plus an alert when a new one appears. Which managed service fits?
Show answer and explanation
Answer: B
Error Reporting reads exception stack traces written to Cloud Logging and groups similar ones into a single issue with occurrence counts. It can notify the team when a new error type appears, and it links each group to the underlying log entries. Logged exceptions are recognized automatically when their stack traces are formatted correctly, so no separate agent is required.
Why the other options are wrong
- A. Trace measures request timing across services and shows where latency accumulates. It does not group exception stack traces or track error counts.
- C. Build runs pipeline steps such as tests and image builds. It reports on build outcomes, not on runtime exceptions in a live service.
- D. Deploy manages delivery of releases across environments. It has no role in grouping production exceptions from a running application.