借助 Error Reporting，您可以自动捕获应用崩溃并将这些崩溃的堆栈轨迹分组到错误组中，以识别、了解和管理应用错误。但是，某些 Google Cloud服务错误会被记录为错误消息，不会以堆栈轨迹的形式提供。Error Reporting 的服务错误功能会自动捕获这些类型的 Google Cloud 服务错误并对其进行分组，以便您快速识别系统中的问题并在出现新错误时收到通知。
例如，您在使用 Cloud Run 时可能会遇到以下情况：在发出请求时达到容器实例数上限。当此事件记录到 Cloud Logging 中时，Error Reporting 中的服务错误会自动捕获此错误，将其与类似错误归为一组，并通知您此事件的发生。此外，为帮助解决这些错误，一些 Google Cloud 服务提供了问题排查文档，您可以从 Error Reporting 页面访问这些文档。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-11。"],[[["\u003cp\u003eError Reporting automatically captures and groups application crashes and stack traces, and can also capture errors from Google Cloud services.\u003c/p\u003e\n"],["\u003cp\u003eService Errors in Error Reporting identifies Google Cloud service errors logged as messages, grouping similar ones to facilitate problem identification and notification.\u003c/p\u003e\n"],["\u003cp\u003eError Reporting offers access to troubleshooting documentation from certain Google Cloud services, aiding in error resolution.\u003c/p\u003e\n"],["\u003cp\u003eThe Error Reporting console displays service errors, including information in the "Type" column when a new service error is detected.\u003c/p\u003e\n"],["\u003cp\u003eService Errors captures various issues from different Google Cloud services, such as Dataflow's worker throttling and Cloud Run's memory limit exceeded errors, among many others.\u003c/p\u003e\n"]]],[],null,["Error Reporting enables you to identify, understand, and manage\napplication errors by automatically capturing application crashes and grouping\nthe stack traces from these crashes into error groups. Some Google Cloud\nservice errors, however, are logged as error messages and don't come in the form\nof stack traces. Error Reporting's Service Errors feature automatically\ncaptures and groups these kinds of Google Cloud service errors so that you can\nquickly identify issues in your system and be notified when new errors occur.\n\nFor example, you might encounter a situation when using Cloud Run in\nwhich you reach your maximum container instance limit when making a request.\nWhen this event is logged to Cloud Logging, Service Errors in\nError Reporting automatically captures this error, groups it with\nsimilar errors, and notifies you that this event has occurred. Additionally, to\nhelp resolve these errors, some Google Cloud services provide troubleshooting\ndocumentation that you can access from the Error Reporting page.\n\nView service errors\n\nIn the Google Cloud console, go to the **Error Reporting** page:\n\n[Go to **Error Reporting**](https://console.cloud.google.com/errors)\n\n\u003cbr /\u003e\n\nYou can also find this page by using the search bar.\n\nWhen Error Reporting detects and groups a log containing a new service\nerror, you can see these service errors on the Error Reporting overview\npage in the **Type** column.\n\nFor service errors with documented solutions, Error Reporting provides\na link to the Troubleshooting guide provided by the Google Cloud service.\n\nSample service errors\n\nThe following table lists some, but not all, of the errors that\nError Reporting's Service Errors captures.\n\n| Google Cloud service name | Error type |\n|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Dataflow | Worker logs throttling Out of memory (system) Missing custom subnet Lengthy operation in step JRE Crash Worker JAR file misconfigured |\n| Cloud Run | Memory limit exceeded No instances available |\n| 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 |"]]
