Error Reporting lets you identify, understand, and manage application failures by automatically capturing application crashes and grouping the stack traces from these crashes into error groups. Error Reporting Service Errors automatically captures failure information from Google Cloud services when they write log entries where failure information is included as error messages, instead of as a stack trace.
For example, suppose you use Cloud Run and you reach your maximum container instance limit when you make a request. The failure of the request is recorded in a log entry and Error Reporting automatically captures this error event, groups it with similar error events, and notifies you. To resolve service-related error events, use the service-specific troubleshooting documentation that is accessible from the Error Reporting page.
View service error groups
In the Google Cloud console, go to the Error Reporting page:
You can also find this page by using the search bar.
When Error Reporting determines that there is a service failure,
it groups these error events and sets the type of error to Service error.
The Error Reporting overview displays the type of error along
with other information about the error group:
For service error events with documented solutions, Error Reporting provides a link to the Troubleshooting guide provided by the Google Cloud service.
Sample service error events
The following table lists some, but not all, of the error events that Error Reporting's Service Errors captures.
| Google Cloud service name | Error type |
|---|---|
| Dataflow | Worker logs throttling Out of memory (system) Missing custom subnet Lengthy operation in step JRE Crash Worker JAR file misconfigured |
| Cloud Run | Memory limit exceeded No instances available |
| Google Kubernetes Engine | Unhealthy pod, failed probe Pods failed scheduling Restarting failed container with backoff Unmounted volume Container image pull failed Failed to update endpoint Secrets/configmaps not found |