Skip to main content
Sumo Logic

Collect Logs for Google Compute Engine

Instructions for configuring log collection for the Sumo Logic App for Google Compute Engine.

This page has instructions for configuring Google Compute Engine to send logs to Sumo.

Configure Google Compute Engine to export logs to Stackdriver   

If you haven't already done so, set up Google Cloud Audit to export logs to Stackdriver. For more information, see Overview of Logs Export in GCP.

Set up a Google-validated HTTP source and Pub/Sub topic   

In this step, you set up an HTTP source in Sumo, register it with Google, and create a Pub/Sub topic to send data to the HTTP source. Follow the instructions in Google Cloud Platform Source.

When you create the HTTP Source, assign a Source Category of “GCP”.

Create export of Google Compute Engine logs from Stackdriver

  1. Go to Logging and click Exports.
  2. Click Create Export.
  3. Select a GCP service to filter the logs. The recommended GCP service to create sinks for is "GCE VM Instance", which sends the service’s logs to Sumo Logic. In the Edit Export window on the right:

    1. Set the Sink Name. For example, "gce-vm-instance".
    2. Select "Cloud Pub/Sub" as the Sink Service.
    3. Set Sink Destination to the newly created Pub/Sub topic. For example, "pub-sub-logs".
    4. Click Create Sink.

Sample Log Message

         "callerSuppliedUserAgent":"Managed Infrastructure Mixer Client"

Query Sample

Top 10 users

_collector="HTTP Source for GCP Pub/Sub" logName resource timestamp
| json "" as type 
| parse regex "\s+\"logName\":\"(?<log_name>\S+)\"" 
| where type = "gce_instance" and log_name matches "projects/*/logs/"
| parse regex "\s+\"resourceName\":\"projects/\S+/zones/(?<zone>\S+)/instances/(?<instance>\S+)\""
| json "" as labels
| json field=labels "project_id" as project
| json "" as user
| count as requests by user
| sort by requests
| limit 10