Google Cloud Logging (om_googlelogging)
Google Cloud Logging is a managed service that stores and analyzes log data from applications hosted on Google Cloud and Amazon Web Services.
The Google Cloud Logging API enables you to write logs to Cloud Logging. This module uses the REST version of the API to send events in batches, reducing HTTP response latency, thus improving data throughput.
|To examine the supported platforms, see the list of installer packages in the Available Modules chapter.|
om_googlelogging requires a Google Cloud service account and a corresponding private key file in JSON format to connect to the Cloud Logging API. Follow these instructions to create a new service account and download its private key file for an existing project.
Log in to your Google Cloud account and switch to the project you want to configure.
From the navigation menu, click on IAM & Admin > Service Accounts.
Click CREATE SERVICE ACCOUNT.
Enter a service account name and description and click CREATE AND CONTINUE.
Select the Owner role from the Role drop-down and click DONE.
Click on the newly created account on the Service accounts page to open its configuration page.
Click the KEYS tab, expand the ADD KEY drop-down and select Create new key.
Select JSON for the key type and click CREATE to download the private key. Save the private key file to a location accessible by NXLog. This file is required for the NXLog configuration.
This mandatory directive specifies the path to the private key file of the service account required for authenticating with the Cloud Logging API. See Configuring a Google Cloud service account for more information.
This mandatory directive specifies the name of the log source on Google Cloud. It accepts a string in the format
<YOURPROJECTNAME>is the name of your Google Cloud project and
<LOG_ID>is the log source name. See Logging query language in the Google Cloud documentation for more information.
This mandatory group directive specifies the Google Cloud resource that produced the log entry. See resources list to get all available values. For example, specify the monitored resource that owns the database to collect its error logs.
<Resources> type gce_instance <labels> zone us-cental </labels> </Resources>
Number of allowed parallel HTTP connections. More connections means bigger throughput, but you need to be sure to not hit the Google Cloud Logging API quotas. The default is 1.
Maximum size of the request in bytes. The default is 65 KB.
A list of key-value pairs for providing event metadata. The labels can be user-defined or system-defined.
User-defined labels are optional key-value pairs that you can use to enrich logs. System-defined labels are defined by Google Cloud Platform (GCP) services for platform logs and are in the format
Cloud Logging truncates label keys that exceed 512 B and label values that exceed 64 KB and replaces the truncated text with an ellipsis (
<Labels> zone us-central1-a </Labels>
This optional directive sets the reconnect interval in seconds. If it is set, the module attempts to reconnect in every defined second. If it is not set, the reconnect interval will start at 1 second and doubles on every attempt. If the duration of the successful connection is greater than the current reconnect interval, then the reconnect interval will be reset to 1 sec.
This configuration uses the om_googlelogging output module to forward logs from the project
myproject to Google Cloud Logging.
<Output google_logging> Module om_googlelogging CredentialsFile /path/to/credentials.json (1) LogName projects/myproject-343509/logs/test <Labels> (2) zone us-central </Labels> <Resources> (3) type gce_instance </Resources> </Output>
|1||Credentials file for authenticating with the Cloud Logging API. See Configuring a Google Cloud service account for more information.|
|2||List of labels defined as key-value pairs to attach to the event.|
|3||List of resources to attach to the event.|