Error Reporting aggregates and displays errors produced in your running Cloud Run services. Cloud Run is automatically integrated with Error Reporting with no setup or configuration required.
The following errors are automatically visible:
- All exceptions that include a stack trace in Error Reporting-supported
languages, and that are sent to
stderr, or to other logs.
- "Memory limit exceeded" and "No instances available" service errors.
You should handle errors and exceptions that occur during requests. Allowing such errors to crash your application process results in a cold start where a new container instance is started up.
Viewing errors in Cloud Run
The "Metrics" tab of the service detail page includes a table showing the top errors for this service that Error Reporting has detected and aggregated.
Viewing errors in Error Reporting
You can view errors after Error Reporting has aggregated them. For details, see Viewing Errors.
To review your current errors, go to the Error Reporting page in the Cloud console:
For more details
For information, see the Error Reporting documentation.