로그 항목이 프로젝트로 라우팅된 후 프로젝트가 해당 로그 항목을 소유 로그 버킷에 저장했습니다.
CMEK가 사용 설정된 로그 버킷에 로그 항목을 저장하는 경우에도 Error Reporting을 사용할 수 있습니다. 하지만 Error Reporting 클라이언트 라이브러리 또는 Error Reporting API를 사용해야 합니다. 자세한 내용은 Error Reporting API 개요 및 Error Reporting 클라이언트 라이브러리를 참조하세요.
가상 프라이빗 클라우드 지원
Error Reporting은 Virtual Private Cloud(VPC) 지원 서비스입니다.
데이터 무단 반출 위험을 줄이려면 VPC 서비스 제어를 사용하여 Google 관리형 서비스에 서비스 경계를 만듭니다.
VPC 서비스 제어 및 서비스 매개변수 만들기 방법에 대한 자세한 내용은 VPC 서비스 제어 문서를 참조하세요.
Error Reporting API 메서드 report 또는 Cloud Logging API 메서드 write를 실행하여 Google Cloud 프로젝트에 오류 이벤트를 보고할 수 있습니다.
API 키 기반 인증이 필요한 경우 Error Reporting API를 사용해야 합니다. Error Reporting API를 사용하여 오류 이벤트를 보고하려면 report 메서드를 실행하고 메서드의 요청 본문 형식을 ReportedErrorEvent 객체로 지정합니다.
Error Reporting API를 사용하는 경우 올바른 형식의 오류 메시지가 포함된 로그 항목이 자동으로 생성되고 Cloud Logging에 기록됩니다. 이러한 로그 항목은 logName과 같이 형식이 지정된 로그에 기록됩니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-04-22(UTC)"],[[["\u003cp\u003eError Reporting supports various environments and offers language-specific client libraries for application developers to send error reports.\u003c/p\u003e\n"],["\u003cp\u003eError data can be sent through language-specific client libraries, automatically-collected log entries, or by directly using the Cloud Logging API or the Error Reporting API.\u003c/p\u003e\n"],["\u003cp\u003eError Reporting is a global service built on Cloud Logging that analyzes log entries under specific conditions, like assured workloads and CMEK being disabled or in a properly configured bucket.\u003c/p\u003e\n"],["\u003cp\u003eError Reporting supports Virtual Private Cloud (VPC), and VPC Service Controls can be used to enhance security.\u003c/p\u003e\n"],["\u003cp\u003eThere are dedicated guides for configuring environments and instrumenting apps, as well as for using the Error Reporting API and Cloud Logging API to write error data, each with their own set of requirements.\u003c/p\u003e\n"]]],[],null,["This document lists the environments supported by Error Reporting and\nit links to language-specific guides for application developers.\nWe recommend that you use the [language-specific client libraries](#libraries)\nor rely on automatically-collected log entries; however, you can\n[write error data with the Cloud Logging API or the Error Reporting API](#apis).\nFor example, if you use\n[Cloud Run](/error-reporting/docs/setup/cloud-run),\nthen exceptions written to `stderr` are automatically sent to Cloud Logging.\n\nError Reporting is a global service built on\nCloud Logging and can analyze log entries when all of the following are true:\n\n- Assured workloads are disabled. For more information, see [Overview of Assured Workloads](/assured-workloads/docs/overview).\n- [Customer-managed encryption keys (CMEK)](/logging/docs/routing/managed-encryption-storage) are disabled on all log buckets that store the log entry. Error Reporting can't store log entries in log buckets that have CMEK enabled. For information about how to determine the CMEK configuration for a log bucket, see [Verify key enablement](/logging/docs/routing/managed-encryption-storage#verify-key).\n- The log bucket satisfies one of the following:\n - The log bucket is stored in the same project where the log entries originated.\n - The log entries were routed to a project, and then that project stored those log entries in a log bucket that it owns.\n\n\u003cbr /\u003e\n\nVirtual Private Cloud support\n\nError Reporting is a Virtual Private Cloud (VPC) supported\nservice.\n\nTo reduce the risk of data exfiltration, use VPC Service Controls to create a\nservice perimeter around your Google-managed services.\nFor information about VPC Service Controls and how to create a service\nparameter, see the\n[VPC Service Controls documentation](/vpc-service-controls/docs).\n\nConfigure environments to automatically report error data\n\nFor information about environment-specific configuration requirements, see\nthe following guides:\n\n- [App Engine flexible environment](/error-reporting/docs/setup/app-engine-flexible-environment)\n- [App Engine standard environment](/error-reporting/docs/setup/app-engine-standard-environment)\n- [Apps Script](/error-reporting/docs/setup/apps-script)\n- [Cloud Run functions](/error-reporting/docs/setup/cloud-functions)\n- [Cloud Run](/error-reporting/docs/setup/cloud-run)\n- [Compute Engine](/error-reporting/docs/setup/compute-engine)\n- [Google Kubernetes Engine](/error-reporting/docs/setup/kubernetes-engine)\n- [Amazon EC2](/error-reporting/docs/setup/ec2)\n\nInstrument apps by using client libraries\n\nFor information about how to configure your application to send error reports,\nsee the language-specific configuration guides:\n\n- [Go apps](/error-reporting/docs/setup/go)\n- [Java apps](/error-reporting/docs/setup/java)\n- [.NET apps](/error-reporting/docs/setup/dotnet)\n- [Node.js apps](/error-reporting/docs/setup/nodejs)\n- [Python apps](/error-reporting/docs/setup/python)\n- [PHP apps](/error-reporting/docs/setup/php)\n- [Ruby apps](/error-reporting/docs/setup/ruby)\n\nWrite error data by using an API\n\nYou can report error events to your Google Cloud project by\nexecuting the Error Reporting API method\n[`report`](/error-reporting/reference/rest/v1beta1/projects.events/report)\nor the Cloud Logging API method\n[`write`](/logging/docs/reference/v2/rest/v2/entries/write).\n\n- If you require API key-based authentication, then you must use the\n Error Reporting API. To report an error event by using the\n Error Reporting API, execute the method\n [`report`](/error-reporting/reference/rest/v1beta1/projects.events/report)\n and format the request body of the method as a\n [`ReportedErrorEvent`](/error-reporting/reference/rest/v1beta1/projects.events/report#ReportedErrorEvent) object.\n\n When you use the Error Reporting API, log entries with properly\n formatted error messages are automatically generated and written to\n [Cloud Logging](/logging/docs). These log entries are written to a log\n whose `logName` is formatted as follows: \n\n ```\n projects/PROJECT_ID/clouderrorreporting.googleapis.com%2Freported_errors\n ```\n\n Because log entries are generated by calls to `report`, you might incur\n Cloud Logging ingestion costs. To control which log entries are ingested,\n see [Exclusion filters](/logging/docs/routing/overview#exclusions).\n\n If you report error events by using the Error Reporting API,\n the remainder of this document doesn't apply.\n- If you want to use the Cloud Logging API, then you must format the\n [`LogEntry`](/logging/docs/api/reference/rest/v2/LogEntry) object so that includes a stack trace,\n or a [`ReportedErrorEvent`](/error-reporting/reference/rest/v1beta1/projects.events/report#ReportedErrorEvent) object. For more information\n about the formatting requirements, see\n [Format errors in logs](/error-reporting/docs/formatting-error-messages)."]]
