Managing errors

This page explains how you can manage your errors in Error Reporting.

To view your errors, open the Error Reporting page in the Cloud Console. A list of recently occurring error groups, in order of frequency, appears:

The user interface showing the error list.

Tip: Treat this list like an email inbox. Keep it clean and useful by fixing underlying errors, and/or muting those errors that are expected and recurring.

For more information on viewing and filtering in your Error Reporting list, go to Viewing errors.

For information on the permissions needed to manage your errors, review the Access control guide.

Error samples

Errors that are grouped together are usually very similar, so Error Reporting keeps only 1,000 samples and extrapolates the remaining information. To keep all occurrences of an error, consider exporting your logs to BigQuery so that future occurrences of the error are saved.

For each sample, the UI shows the data that your application sends to Error Reporting. For example, App Engine standard provides useful metadata like the user agent and the URL of the request that led to the error. If you are sending your own error reports as log entries, check the list of fields you can provide. If you are using the Error Reporting API, refer to the ReportedErrorEvent object.

For more information, go to How errors are grouped.

Changing resolution status

To manage your workflow, change the resolution status of your error groups by doing the following:

  1. Go to the Operations > Error Reporting page in the Cloud Console:

    Go to the Error Reporting page

  2. For each error group, Resolution status appears:

    The user interface showing the error resolution status.

  3. In the preceding panel, expand the Resolution status column to change the status of an error group. Following are the possible status values:

    • Open: The default initial state of all error groups. The other states are set manually. You can revert an error group's status back to Open at any time.
    • Acknowledged: A state for triaging error groups.
    • Resolved: A state for indicating that an error group is fixed and no longer expected to occur. If an error group marked as Resolved later reoccurs, Error Reporting changes the resolution status back to Open.
    • Muted: A state for hiding an error group from your list. For more information, go to Muting errors.

Muting errors

You can hide an error group from your Error Reporting list by changing its resolution status to Muted. Muted errors won't reappear in your list, even if they reoccur.

To view your muted error groups (and unmute them if desired), do the following:

  1. Click Manage muted errors:

    The user interface showing the muted errors menu.

  2. The Muted Errors page appears. In the top navigation bar, expand the Resolution status panel. Select the resolution status types of the error groups that you wish to hide from your list.

    The user interface showing the resolution status muting option.

To unmute an error group, deselect its resolution status type from the same Resolution status panel.

Error Reporting won't send notifications if the muted error reoccurs.

Linking to issues

You can link error groups to issues.

To view or change the issue(s) associated with an error group, click the bug report icon next to each row in your list:

The user interface showing the bug icon.

If the error group is not yet associated with an issue URL, clicking on the bug report icon opens a Link an issue URL to this error panel, where you can type in the appropriate URL.

If an error group is already associated with an URL in your issue tracker system, clicking on the bug report icon opens that link in a new browser tab.


Error Reporting can notify you when new errors occur and when errors that have been marked Resolved reoccur. To learn more, go to Notifications.

Deleting errors

You can delete all error events which are stored for the given project, and reset error counts to zero, using either the gcloud tool or the REST API.


To delete all error events:

gcloud beta error-reporting events delete


To delete all error events, use the projects.deleteEvents method of the REST API.