Raccogliere i dati sugli errori utilizzando Error Reporting
Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Questo documento elenca gli ambienti supportati da Error Reporting e
fornisce link a guide specifiche per lingua per gli sviluppatori di applicazioni.
Ti consigliamo di utilizzare le librerie client specifiche per la lingua
o di fare affidamento sulle voci di log raccolte automaticamente. Tuttavia, puoi
scrivere dati di errore con l'API Cloud Logging o l'API Error Reporting.
Ad esempio, se utilizzi
Cloud Run,
le eccezioni scritte in stderr vengono inviate automaticamente a Cloud Logging.
Error Reporting è un servizio globale basato su
Cloud Logging e può analizzare le voci di log quando sono vere tutte le seguenti condizioni:
Il bucket di log soddisfa una delle seguenti condizioni:
Il bucket di log viene archiviato nello stesso progetto in cui hanno avuto origine le voci di log.
Le voci di log sono state instradate a un progetto, che le ha archiviate
in un bucket di log di sua proprietà.
Supporto di Virtual Private Cloud
Error Reporting è un servizio supportato da Virtual Private Cloud (VPC).
Per ridurre il rischio di esfiltrazione di dati, utilizza i Controlli di servizio VPC per creare un perimetro di servizio attorno ai servizi gestiti da Google.
Per informazioni sui Controlli di servizio VPC e su come creare un parametro di servizio, consulta la documentazione sui Controlli di servizio VPC.
Configurare gli ambienti per segnalare automaticamente i dati sugli errori
Per informazioni sui requisiti di configurazione specifici per l'ambiente, consulta le seguenti guide:
Per informazioni su come configurare l'applicazione per l'invio di report sugli errori,
consulta le guide alla configurazione specifiche per la lingua:
Puoi segnalare gli eventi di errore al tuo progetto Google Cloud eseguendo il metodo dell'API Error Reporting report o il metodo dell'API Cloud Logging write.
Se richiedi l'autenticazione basata su chiave API, devi utilizzare l'API Error Reporting. Per segnalare un evento di errore utilizzando l'API Error Reporting, esegui il metodo report e formatta il corpo della richiesta del metodo come oggetto ReportedErrorEvent.
Quando utilizzi l'API Error Reporting, le voci di log con messaggi di errore formattati correttamente vengono generate e scritte automaticamente in Cloud Logging. Queste voci di log vengono scritte in un log
il cui logName è formattato come segue:
Poiché le voci di log vengono generate dalle chiamate a report, potresti incorrere in costi di importazione di Cloud Logging. Per controllare quali voci di log vengono importate,
consulta Filtri di esclusione.
Se segnali gli eventi di errore utilizzando l'API Error Reporting,
il resto di questo documento non si applica.
Se vuoi utilizzare l'API Cloud Logging, devi formattare l'oggetto
LogEntry in modo che includa una analisi dello stack o un oggetto
ReportedErrorEvent. Per maggiori informazioni
sui requisiti di formattazione, consulta
Errori di formato nei log.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-03 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)."]]
