Google Cloud Logging Details Test
Cloud Logging is a fully managed service that allows you to store, search, analyze, monitor, and alert on logging data and events from Google Cloud. Logging includes storage for logs through log buckets, a user interface called the Logs Explorer, and an API to manage logs programmatically. Logging lets you read and write log entries, query logs, and control how you route and use your logs.
By monitoring Google Cloud Logging, you can gain actionable insights into the performance, availability, and behavior of your applications and infrastructure on Google Cloud Platform. These services help you detect and respond to issues quickly, optimize resource utilization, and ensure the reliability of cloud-based systems. Problems in the logging service such as failures, errors, excessive storage consumption, etc., can render Google Cloud Platform data unavailable. To avoid this, administrators should rapidly capture and troubleshoot issues with the logging service. The Google Cloud Logging Details test continuously monitors the logging service and alerts administrators to excessive data ingestion, log entry failures, errors, etc., so they can resolve the issues before any serious issue occurs.
Note:
This test will report metrics only if the Cloud Logging API is enabled in the target Google Cloud project. If you want to know how to turn on a service API in the Google Cloud project, refer Enabling Service APIs.
Target of the test : Google Cloud
Agent deploying the test : A remote agent
Outputs of the test : One set of results for the Google Cloud project being monitored
| Parameters | Description |
|---|---|
|
Test Period |
How often should the test be executed. |
|
Host |
The host for which the test is to be configured. |
|
Private Keyfile Name |
To connect to the Google Cloud Project in which the services are running, the eG agent requires a private key of a service account with Compute Viewer, Monitoring Viewer, and Cloud Asset Viewer roles in the target project. If a service account pre-exists in the project, then you can download the private key as a JSON file. Save this JSON file in the <eG_Install_Dir>/agent/lib folder and provide the name of that file against this parameter. However, if no such service account pre-exists, you will have to create one for monitoring the project. To know how to create a service account and download its private key, refer to How does eG Enterprise Monitor Google Cloud?. |
| Measurement | Description | Measurement Unit | Interpretation | ||||||
|---|---|---|---|---|---|---|---|---|---|
|
Log bytes ingested |
Indicates the volume of billing log bytes ingested into Google Cloud Logging during the last measurement period. |
MB |
This metric is commonly used to track the amount of data being collected and stored by the logging service, providing insights into the logging activity and the overall workload. |
||||||
|
Logging storage volume |
Indicates the total amount of billing log data stored within the logging service. |
MB |
|
||||||
|
Log bucket bytes ingested |
Indicates the total volume of billing log data ingested into a specific logging bucket during the last measurement period. |
MB |
|
||||||
|
Log bucket monthly bytes ingested |
Indicates the total volume of billing log data ingested into a specific logging bucket over the period of a month. |
MB |
|
||||||
|
Monthly log bytes ingested |
Indicates the total volume of billing log bytes ingested into the logging service over the duration of a month. |
MB |
|
||||||
|
Log bytes ingested |
Indicates the amount of log bytes ingested into a logging service during the last measurement period. |
MB |
|
||||||
|
Exported log bytes |
Indicates to the total volume of log data that was exported from the logging service to external storage destinations, such as Google Cloud Storage, BigQuery, or Pub/Sub during the last measurement period. |
MB |
This measure sheds light on the export activity of Google Cloud Logging infrastructure and enables you to effectively manage logging resources, analyze log data, and integrate logging with other systems and services in Google Cloud Platform. |
||||||
|
Exported log entries failures |
Indicates the number of times that the log entries failed to be exported from the logging service to external storage destinations. |
Number |
Ideally, the value of this measure should be very low. These failures can occur due to various reasons, such as network issues, destination service availability problems, misconfiguration, or resource constraints. Monitoring and addressing these failures are crucial to ensure the integrity, reliability, and compliance of log data export processes. |
||||||
|
Exported log entries |
Indicates the number of log entries that were successfully exported from the logging service to the external storage destinations during the last measurement period. |
Number |
|
||||||
|
Log entries ingested |
Indicates the total number of log entries that were ingested into the logging service during the last measurement period. |
Number |
|
||||||
|
Logs-based metric errors |
Indicates the number of errors occurred while processing logs-based metrics within the logging service during the last measurement period. |
Number |
A non-zero value for this measure is a cause for concern. |
||||||
|
Logs-based metric active cardinality count by label |
Indicates the count of active cardinalities for a specific label in logs-based metrics within the logging service. |
Number |
|
||||||
|
Logs-based metric label throttled status |
Indicates whether/not throttling is applied to labels within logs-based metrics in the logging service. |
|
The values that this measure reports and their corresponding numeric values are listed below:
Note: This measure reports the Measure Values listed in the table above to indicate the throttling status of the labels within logs-based metrics. In the graph of this measure however, the same is indicated using the numeric equivalents only. |
||||||
|
Logs-based metric throttled status |
Indicates the whether/not throttling is applied to the logs-based metrics in within the logging service. |
|
The values that this measure reports and their corresponding numeric values are listed below:
Note: This measure reports the Measure Values listed in the table above to indicate the throttling status of the logs-based metrics. In the graph of this measure however, the same is indicated using the numeric equivalents only. |
||||||
|
Logs-based metric active time series (cardinality) count |
Indicates the number of distinct time series that is currently contributing to the logs-based metrics in the logging service. |
Number |
This value provides insights into the complexity and granularity of the metric data, helping you understand the diversity of log data and the distribution of metric values. |
