Google Cloud Provider Log Ingestion Overview
Last updated - 21 November, 2025
Using Google Cloud Provider (GCP) logs to monitor activities such as system health, performance, security events, and compliance is a valuable method to obtain information about your environment.
Configuring the GCP log ingestion to integrate with LogicMonitor involves the following process:
- Exporting GCP logs
- Creating a GCP log sink
- Connecting to Pub/Sub
- Forwarding logs using Fluentd
- Mapping logs to your monitored GCP resources
For more information, see Google Cloud Provider Log Ingestion Configuration.
LM Logs supports the following resources and log types:
- GCP audit logs
- GCP Cloud Composer logs
- GCP Cloud Function logs
- GCP Cloud Run logs
- GCP CloudSQL logs
- Virtual Machine (VM) instance logs
General Requirements for Ingesting Google Cloud Provider Logs
To ingest GCP logs into LogicMonitor, you need the following:
- A LogicMonitor API token to authenticate all requests to the log ingestion API. For more information, see Adding an API Token
- Access to the GCP account created in your LogicMonitor portal that forwards logs
- IAM roles in GCP to create the virtual machine, log sinks, and Pub/Sub topics
