Version 3.3.0

• 4.3.0 (latest)
• 4.2.0
• 4.1.0
• 4.0.0
• 3.6.0
• 3.5.0
• 3.4.0
• 3.3.0

Google.Cloud.Logging.V2

Google.Cloud.Logging.V2 is a.NET client library for the Google Cloud Logging API.

Note: This documentation is for version 3.3.0 of the library. Some samples may not work with other versions.

• Integration with log4net is provided by the Google.Cloud.Logging.Log4Net package.
• Integration with NLog is provided by the Google.Cloud.Logging.NLog package.

Installation

Install the Google.Cloud.Logging.V2 package from NuGet. Add it to your project in the normal way (for example by right-clicking on the project in Visual Studio and choosing "Manage NuGet Packages...").

If you wish to use the log4net integration, install the Google.Cloud.Logging.Log4Net package in the same way.

Authentication

When running on Google Cloud Platform, no action needs to be taken to authenticate.

Otherwise, the simplest way of authenticating your API calls is to download a service account JSON file then set the GOOGLE_APPLICATION_CREDENTIALS environment variable to refer to it. The credentials will automatically be used to authenticate. See the Getting Started With Authentication guide for more details.

Support from third party libraries

• Logary supports Google Stackdriver logging. Install the NuGet package and see instructions on the project homepage.
• Serilog supports Google Stackdriver Logging. Install the NuGet package Serilog.Sinks.GoogleCloudLogging and configure options.

Raw RPC API

If required, this package provides a low-level abstraciton over the raw RPC API.

All operations are performed through the following client classes:

• ConfigServiceV2Client
• LoggingServiceV2Client
• MetricsServiceV2Client

Create a client instance by calling the static Create or CreateAsync methods. Alternatively, use the builder class associated with each client class (e.g. ConfigServiceV2ClientBuilder for ConfigServiceV2Client) as an easy way of specifying custom credentials, settings, or a custom endpoint. Clients are thread-safe, and we recommend using a single instance across your entire application unless you have a particular need to configure multiple client objects separately.