To see your errors, open the Stackdriver Error Reporting page in the Google Cloud Platform Console. A list of recently occurring errors, in order of frequency, is displayed:
Errors are grouped and de-duplicated by analyzing their stack traces. Our system knows about the common frameworks used for your language and groups errors accordingly. For more information, see How errors are grouped.
Each error entry provides a summary that helps you determine when the application started to produce the error, how often it occurred, and how recently it occurred.
Error Reporting samples up to 1,000 errors per hour. When this limit is reached, the displayed counts are estimated. If too many events are received for the whole day, Error Reporting can sample up to 100 errors per hour and continue to extrapolate the counts.
You can filter, sort, and view additional details about errors, as well as restrict the errors that appear in the list to a specific time range.
Error Reporting list
On the Error Reporting list page, the following information is provided for each reported error:
|Resolution Status||A workflow status assigned at the error-group level. Status options are: Open, Acknowledged, Resolved, and Muted.|
|Occurrences||The number of times this error has occurred in the selected time range.|
|Users||The number of users affected by this error in the selected time range. The column is hidden if no user information is available.|
|Error||Provides the error information, as extracted from the error's stack trace. The error message and its code location are displayed. If your code is available in Cloud Source Repositories, clicking the code location brings you to your source.|
|Seen in||Lists the service and version in which the error is occurring.|
|First seen||The time at which this error first appeared. Sorting on this column is useful for finding the errors which have most recently started occurring.|
|Last seen||The time at which this error last occurred. Sorting on this column is useful for seeing which errors are still occurring. You can also reverse sort to see which have stopped.|
|Response Code||The HTTP status code returned with this error.|
Error Details page
To view detailed information about an error group, click any entry that appears in the Error Reporting list to show the Error Details page:
On this page you can examine information about the error group, including the history of a specific error, specific error instances, and diagnostic information contained in samples for the error. Each sample is one occurrence of the errors. Each sample includes a parsed stack trace and, if available, a link to the associated logs entry.
Error Reporting keeps up to 1,000 samples of an error. When this limit is reached, the displayed counts are estimated.
Filter, sort, and restrict the types of error groups that appear in the list page or details pages. There are several ways to filter your errors from these pages.
Use the Filter errors text field to filter the list of displayed errors. This field performs a text match on the Error information, the HTTP Response Code, the exception stack, and the following attributes:
- Request URL
- Report location (that is, the location where the error was logged)
- HTTP method
On the Error Reporting list page, the bar graph under the Occurrences column updates to show filtered results in blue, versus the non-filtered total in grey:
You can view the bar graph, in detail, on the Error Details page in the Errors section.
Resolution status filtering
Use the Resolution Status column to filter your error groups:
For more information, go to Resolution status.
Other actions to help you view your errors are:
- Link to issue / View issue: These options are accessed from the bug icon next to each row in the list:
- Auto reload: Reloads the list every 10 seconds.