Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://cloud.google.com/error-reporting/docs/setup/dotnet below:

Instrument C# apps for Error Reporting

Stay organized with collections Save and categorize content based on your preferences.

You can send error reports to Error Reporting from C# applications by using the Google.Cloud.Diagnostics set of libraries . Use the Google.Cloud.Diagnostics set of libraries to create error groups for the following cases:

• A log bucket that contains your log entries has customer-managed encryption keys (CMEK).
• The log bucket satisfies one of the following:
  • The log bucket is stored in the same project where the log entries originated.
  • The log entries were routed to a project, and then that project stored those log entries in a log bucket that it owns.
• You want to report custom error events.

Error Reporting is integrated with some Google Cloud services, such as Cloud Functions and App Engine, Compute Engine, and Google Kubernetes Engine. Error Reporting displays the errors that are logged to Cloud Logging by applications running on those services. For more information, go to Running on Google Cloud on this page.

You can also send error data to Error Reporting using Logging. For information on the data formatting requirements, read Formatting error messages in Logging.

1. Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.

2. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

   Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

   Go to project selector

3. Verify that billing is enabled for your Google Cloud project.

4. Enable the Error Reporting API .

   Enable the API

5. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

   Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

   Go to project selector

6. Verify that billing is enabled for your Google Cloud project.

7. Enable the Error Reporting API .

   Enable the API

The Google.Cloud.Diagnostics set of libraries lets you monitor and view errors reported by C# applications running nearly anywhere.

1. For applications that target ASP.NET Core 3 or later, use the Google.Cloud.Diagnostics.AspNetCore3 library. You can install this library from NuGet.
2. For applications that target earlier versions of ASP.NET Core, use the Google.Cloud.Diagnostics.AspNetCore library. You can install this library from NuGet.
3. For applications that target non ASP.NET Core frameworks, use the Google.Cloud.Diagnostics.Common library. You can install this library from NuGet.

For more information on installation, read the documentation for the Google.Cloud.Diagnostics set of libraries . You can also report issues using the issue tracker.

For more information and examples, see the following resources:

To create error groups by using projects.events.report, your service account requires the Error Reporting Writer role (roles/errorreporting.writer).

Some Google Cloud services automatically grant the Error Reporting Writer role (roles/errorreporting.writer) to the appropriate service account. However, you must grant this role to the appropriate service account for some services.

The default service account used by Cloud Run has the permissions of Error Reporting Writer role (roles/errorreporting.writer).

The Google.Cloud.Diagnostics set of libraries can be used without needing to explicitly provide credentials.

Cloud Run is configured to use Error Reporting automatically. Unhandled JavaScript exceptions will appear in Logging and be processed by Error Reporting without needing to use the Google.Cloud.Diagnostics set of libraries .

App Engine grants the Error Reporting Writer role (roles/errorreporting.writer) to your default service account automatically.

The Google.Cloud.Diagnostics set of libraries can be used without needing to explicitly provide credentials.

Error Reporting is automatically enabled for App Engine flexible environment applications. No additional setup is required. Messages written from App Engine to stderr are analyzed and, if found to contain a stack trace, will be displayed by Error Reporting.

See Viewing errors for instructions on viewing error and exception data for your application in the Google Cloud console.

To use Error Reporting with Google Kubernetes Engine, do the following:

1. Ensure that the service account to be used by your container has been granted the Error Reporting Writer role (roles/errorreporting.writer).

   You can use either the Compute Engine default service account or a custom service account.

   For information about granting roles, see Manage access to projects, folders, and organizations.

2. Create your cluster and grant the cluster the cloud-platform access scope.

   For example, the following create command specifies the cloud-platform access scope and a service account:

   gcloud container clusters create CLUSTER_NAME --service-account  SERVICE_ACCT_NAME --scopes=cloud-platform
   

To use Error Reporting with Compute Engine VM instances, do the following:

1. Ensure that the service account to be used by your VM instance has been granted the Error Reporting Writer role (roles/errorreporting.writer).

   You can use either the Compute Engine default service account or a custom service account.

   For information about granting roles, see Manage access to projects, folders, and organizations.

2. In the Google Cloud console, go to the VM instances page:

   Go to VM instances

   If you use the search bar to find this page, then select the result whose subheading is Compute Engine.

3. Select the VM instance that you want to receive the cloud-platform access scope.

4. Click Stop, and then click Edit.

5. In the Identity and API access section, select a service account that has the Error Reporting Writer role (roles/errorreporting.writer).

6. In the Access scopes section, select Allow full access to all Cloud APIs, and then save your changes.

7. Click Start/Resume.

For more information and examples, see the following resources:

To use the Google.Cloud.Diagnostics set of libraries in a local development environment, such as running the library on your own workstation, you must provide your Google.Cloud.Diagnostics set of libraries with the local application default credentials. For more information, see Authenticate to Error Reporting.

To use the .NET samples on this page in a local development environment, install and initialize the gcloud CLI, and then set up Application Default Credentials with your user credentials.

Install the Google Cloud CLI.

If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.

If you're using a local shell, then create local authentication credentials for your user account:

gcloud auth application-default login

You don't need to do this if you're using Cloud Shell.

Note: If the gcloud CLI prints a warning that your account doesn't have the serviceusage.services.use permission, then some gcloud CLI commands and client libraries might not work. Ask an administrator to grant you the Service Usage Consumer IAM role (roles/serviceusage.serviceUsageConsumer), then run the following command:

gcloud auth application-default set-quota-project PROJECT_ID

If an authentication error is returned, and you are using an external identity provider (IdP), confirm that you have signed in to the gcloud CLI with your federated identity.

For more information, see Set up authentication for a local development environment.

The projects.events.report method also supports API keys. If you want to use API keys for authentication, you do not need to set up a local Application Default Credentials file. For more information, see Create an API key in the Google Cloud authentication documentation.

In the Google Cloud console, go to the Error Reporting page:

Go to Error Reporting

You can also find this page by using the search bar.

For more information, see Viewing Errors.

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."],[[["Error Reporting can be used with C# applications to monitor and view errors, utilizing the Google.Cloud.Diagnostics set of libraries."],["The Google.Cloud.Diagnostics libraries offer specialized versions for ASP.NET Core 3+, earlier ASP.NET Core versions, and non-ASP.NET Core frameworks, all installable from NuGet."],["Error Reporting integrates with Google Cloud services like Cloud Functions, App Engine, Compute Engine, and Google Kubernetes Engine, displaying errors logged to Cloud Logging from applications on these services."],["Using Error Reporting on Google Cloud requires the service account to have the Error Reporting Writer role, which some services automatically grant, while others require manual assignment."],["For local development, applications using Google.Cloud.Diagnostics libraries need to be authenticated using Application Default Credentials, or you can opt to use API keys instead."]]],[]]

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