Stay organized with collections Save and categorize content based on your preferences.
You can send errors from your Compute Engine applications to Error Reporting in one of two ways:
By logging to Cloud Logging. If you're already using Cloud Logging, the only additional requirement is that your log entries be recognizable by Error Reporting. For more information on error formatting requirements, read Formatting errors in Cloud Logging.
Using the Error Reporting API. Your application can send HTTP requests using the REST API, or can make use of experimental libraries in several languages.
To connect your Compute Engine applications to Error Reporting, send your exceptions or other errors to Logging.
For example:
google-fluentd
agent as is appropriate for your environment. For instructions, see Installing the Logging agent.Modify your application so that it logs exceptions and their stack traces to Logging.
You must include all the information for a single error or exception in the same log entry, including all the frames of any stack trace. If all the information isn't together, then Error Reporting might not detect the error. You can use the structured JSON format for your log entry payloads to include different kinds of information for each error.
Add the following to your pom.xml
file:
Then use code like the following to send the exception data:
PythonFirst, install the fluent-logger-python
library:
sudo pip install fluent-logger
Then use code like the following to send the exception data:
Node.jsFirst, install the fluent-logger-node
library:
npm install fluent-logger
Then use code like the following to send the exception data:
GoFirst, install the fluent-logger-golang
package:
go get github.com/fluent/fluent-logger-golang/
Then use code like the following to send error data:
Using the Error Reporting API to write errorsThe Error Reporting API provides a report
endpoint for writing error information to the service.
Enable the Error Reporting API.
Report errors to the API using either the REST API or a client library.
The ASP.NET NuGet package reports uncaught exceptions from ASP.NET web applications to Error Reporting.
Install the NuGet packageTo install the Stackdriver ASP.NET NuGet package in Visual Studio:
Google.Cloud.Diagnostics.AspNet
.Once you've installed the Stackdriver ASP.NET NuGet package, add the following statement to your application code to start sending errors to Stackdriver:
using Google.Cloud.Diagnostics.AspNet;
Add the following HttpConfiguration
code to the Register
method of your .NET web app (replacing your-project-id
with your actual project ID to enable the reporting of exceptions:
Once you've added this method to your ASP.NET application, you can view any uncaught exceptions that occur as they get reported to Google Cloud in the Error Reporting section of the Google Cloud console.
C#The following example can be found in the GoogleCloudPlatform/dotnet-docs-samples repo. To use it, after building the project, specify your project ID:
C:\...\bin\Debug> set GOOGLE_PROJECT_ID=[YOUR_PROJECT_ID]
Make sure to replace [YOUR_PROJECT_ID]
with the correct value from the Google Cloud console.
Then, send exception data with code similar to the following:
GoSee Setting up Error Reporting for Go.
JavaSee Setting up Error Reporting for Java.
Node.jsSee Setting up Error Reporting for Node.js.
RubySee Setting up Error Reporting for Ruby.
PythonSee Setting up Error Reporting for Python.
PHPSee Setting up Error Reporting for PHP.
View error groupsIn the Google Cloud console, go to the Error Reporting page:
You can also find this page by using the search bar.
Note: If you see the message "Set up Error Reporting" on the Error Reporting page, then your Google Cloud project has no error groups to display.Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-11 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-11 UTC."],[[["Compute Engine applications can send errors to Error Reporting by logging to Cloud Logging, which requires the log entries to be formatted correctly for recognition."],["Alternatively, applications can directly use the Error Reporting API, which includes options for sending HTTP requests via the REST API or using experimental client libraries in multiple programming languages."],["When using Cloud Logging, it's necessary to install the `google-fluentd` agent and modify the application to log exceptions and stack traces to Cloud Logging, ensuring all information for a single error is included in one log entry."],["Using the Error Reporting API requires enabling the API in the Google Cloud Console and reporting errors using either the REST API or client libraries, with examples provided for languages such as ASP.NET and C#."],["The Error Reporting page in the Google Cloud console allows users to view error groups, but will display a setup message if there are no errors to display."]]],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4