Error Reporting aggregates and displays errors produced in your running
Cloud Run resources. Cloud Run automatically integrates
with Error Reporting with no setup or configuration required.

The following errors are automatically visible:

1. All exceptions that include a stack trace in [Error Reporting-supported languages](https://docs.cloud.google.com/error-reporting/docs/setup.md.txt) , and that are sent to `stdout`, `stderr`, or to other logs.
2. "Memory limit exceeded" and "No instances available" [service errors](https://docs.cloud.google.com/error-reporting/docs/service-errors.md.txt).

You should handle errors and exceptions that occur during requests. Allowing
such errors to crash your application process results in a
[cold start](https://docs.cloud.google.com/run/docs/tips#starting_services_quickly) where a new container
instance starts up.

## View errors in Error Reporting

View errors after Error Reporting aggregates them. For
details, see [Viewing Errors](https://docs.cloud.google.com/error-reporting/docs/viewing-errors.md.txt).

To review your current errors, go to the Error Reporting page in the
Google Cloud console:

[Go to Error Reporting](https://console.cloud.google.com/errors)

For information, see the [Error Reporting documentation](https://docs.cloud.google.com/error-reporting/docs.md.txt).

## View errors in Cloud Run console (services only)

To view top errors that Error Reporting has detected and aggregated for
a Cloud Run service, go to the **Observability** \>
**Errors** tab in the Cloud Run console.