Stream Logs using Pub/Sub

This feature is only available for enterprise plan with inCloud Managed deployment

groundcover is able to ingest natively into the platform using GCP's Pub/Sub features. Follow the instructions below to set up the integration:

1. Get your dedicated Pub/Sub topic details from groundcover's team

2. Create a new sink in Log Router connected to the Pub/Sub topic

3. Share the new sink details with the groundcover team

Retrieving the Pub/Sub topic name

For purposes of the integration, groundcover will provision a new topic in the inCloud Managed project. You will need this topic name when setting up the log router sink in the next step.

Contact the groundcover team to retrieve the topic name

Create a Log Router sink

In the Log Router page in the GCP console, create a new logging sink.

1. Sink Details -

   1. Name - Choose a name that fits your needs. Example: groundcover_logs

2. Sink Destination -

   1. Sink Service - Select Cloud Pub/Sub topic

   2. Click on the Select a Cloud Pub/Sub topic dropdown, and click on Enter topic manually. In the new box fill in the topic name received in the previous step. Example: projects/groundcover-project/topics/groundcover-incloud-gcp-id-topic

3. Choose logs to include in the sink -

   1. Create a filter of your choosing. Example: resource.labels.service_name="my-service-name"

Share sink details with the groundcover team

After creating the new sink, browse back to the Log Router page. You will see the new sink in the list. On the right side of the page, click on More Actions -> View sink details.

Share the Writer identity value with the groundcover team.

groundcover needs the Writer identity to allow the new sink to push logs into the Pub/Sub topic associated with your account.

Browse logs in the groundcover platform

Once the groundcover team finishes the setup, logs will start streaming into your environment, appearing in the native logs screen.

The logs will automatically be enriched with various attributes, two of which will help you quickly find your logs:

1. environmentType will be set as gcp

2. workload will be set as the service name deduced from GCP label resource.labels.service_name