Serilog.Sinks.LazyGoogleCloudLogging 1.0.0

Serilog.Sinks.GoogleCloudLogging

Serilog sink that writes events to Google Cloud Logging.

• Built for net6.0, net5.0, netstandard2.0
• Release Notes

Usage

Install package from Nuget:

dotnet add package Serilog.Sinks.GoogleCloudLogging

Configure in code:

var config = new GoogleCloudLoggingSinkOptions { ProjectId = "YOUR_PROJECT_ID" };
Log.Logger = new LoggerConfiguration().WriteTo.GoogleCloudLogging(config).CreateLogger();

Or configure with config file:

This requires the serilog-settings-configuration package.

"Serilog": {
  "Using": [ "Serilog.Sinks.GoogleCloudLogging" ],
  "MinimumLevel": "Information",
  "WriteTo": [
    {
      "Name": "GoogleCloudLogging",
      "Args": {
        "projectID": "PROJECT-ID-12345",
        "restrictedToMinimumLevel": "Information",
        "labels": {
          "foo": "bar"
        }
      }
    }
  ]
}

var config = new ConfigurationBuilder().AddJsonFile("appsettings.json", optional: true, reloadOnChange: true).Build();
Log.Logger = new LoggerConfiguration().ReadFrom.Configuration(config).CreateLogger();

• Serilog example for .NET 6: https://blog.datalust.co/using-serilog-in-net-6/

GCP Integration

Authentication

This library uses the Google Cloud .NET client and Application Default Credentials. The Logs Writer permission is required to send logs. There are several different ways to set credentials:

• GCE, GKE, Cloud Run, AppEngine and other managed services will have the Application Default Credentials set to the active service account for the resource and can be used without any additional configuration.
• Authenticate manually with the gcloud SDK on a server to set the Application Default Credentials.
• Set the GOOGLE_APPLICATION_CREDENTIALS environment variable to specify the path to your JSON credentials file.
• Set the GoogleCredentialJson config option to pass in a JSON string (the contents of your JSON credentials file).

Log Output

• Serilog is designed for structured logging which is fully supported by Google Cloud. Logs are sent as a JSON object (JsonPayload in the protobuf API) with labels, properties, metadata and any other data like stack traces automatically attached.
• Numeric values in labels and properties will be converted to double during serialization because that is the only numeric type supported by JSON. Large integers and floating-point values will lose precision. If you want the exact value preserved then log it as a string instead.
• GCP Error Reporting is separate from Cloud Logging and will automatically capture error messages only if they have an Exception attached. It is not based on log severity level.
• View logs in the GCP Logs Explorer: https://console.cloud.google.com/logs/viewer

Sink Options

Log Level Mapping

This table shows the mapping from Serilog LogLevel to Google Cloud Logging LogSeverity