Google Cloud telemetry

Squasher can create the Google Cloud log delivery path after OAuth consent and project selection. You can also use the manual drain endpoint when you already have a delivery step.

One-click setup

In Squasher, open Integrations > Google Cloud and select Connect.
Approve Google Cloud access and select one Google Cloud project.
Review the log filter and metric scope.
Confirm setup and run the opt-in verification.

Squasher creates a Pub/Sub topic and authenticated push subscription, then creates a Cloud Logging sink for the selected filter. It grants only the sink writer identity permission to publish to that topic. Squasher reads Cloud Monitoring metrics with read-only monitoring access. The Google OAuth application must be configured for public use. The connecting identity needs access to create Logging sinks and Pub/Sub resources and to change the topic policy. Google can require app verification before users outside the app’s test-user list can connect. Squasher verifies the Google-signed identity token on each Pub/Sub push. Disconnect removes only the sink, subscription, topic, and grants recorded for this connection. See Google Cloud’s log sink and Pub/Sub permission guide.

Google Cloud can charge for Pub/Sub delivery, Cloud Monitoring API use, and related telemetry. Review the selected log filter before you enable a high-volume project.

Overview

Send the Cloud Logging JSON body from your forwarder or delivery step. Squasher accepts either an entries array or a single top-level log entry.

Prerequisites

A Squasher project ID
A Squasher drain key or log connector key for that project
Access to create or update a Cloud Logging sink or Logs Router filter
A delivery step that can POST Cloud Logging JSON to Squasher

Endpoint URL

https://ingest.squasher.ai/v1/drain/gcp/{project_id}

Authentication

Send your drain key in the x-squasher-key header on every request.

x-squasher-key: sq_pk_your_drain_key
Content-Type: application/json

Payload Format

The GCP drain accepts batched entries and direct single-entry requests.

{
  "logName": "projects/demo/logs/run.googleapis.com%2Fstdout",
  "entries": [
    {
      "severity": "ERROR",
      "textPayload": "Unhandled exception in worker",
      "timestamp": "2024-03-21T12:00:00Z"
    }
  ]
}

{
  "logName": "projects/demo/logs/custom",
  "severity": "CRITICAL",
  "jsonPayload": {
    "message": "database connection lost",
    "component": "worker"
  },
  "timestamp": "2024-03-21T12:05:00Z"
}

Manual setup steps

Create or update the sink

In Logging > Logs Router, create a sink or filter that selects the Cloud Logging streams you want to forward.

Choose the delivery step

Use the forwarding step that will POST the Cloud Logging JSON body to Squasher.

Send the payload to Squasher

Configure that delivery step to call the GCP drain endpoint with the x-squasher-key header and the Cloud Logging JSON body shown above.

Working cURL Example

Use this example to verify the drain before you wire in your Cloud Logging delivery flow.

PROJECT_ID="your-project-id"
SQUASHER_KEY="sq_pk_your_drain_key"

curl -X POST "https://ingest.squasher.ai/v1/drain/gcp/${PROJECT_ID}" \
  -H "Content-Type: application/json" \
  -H "x-squasher-key: ${SQUASHER_KEY}" \
  -d '{
    "logName": "projects/demo/logs/run.googleapis.com%2Fstdout",
    "entries": [
      {
        "severity": "ERROR",
        "textPayload": "Unhandled exception in worker",
        "timestamp": "2024-03-21T12:00:00Z"
      }
    ]
  }'

A successful request returns 202 Accepted.

Agent handoff

Set up Cloud Logging forwarding to Squasher for project <project_id>. Use a project-specific drain or connector key, verify with one batched entry payload, and ask before changing sink filters or delivery routing.

Get Started

SDKs

Integrations

Migrations

Cloud Log Drains

Features

API Reference

Google Cloud telemetry

One-click setup

Overview

Prerequisites

Endpoint URL

Authentication

Payload Format

Manual setup steps

Working cURL Example

Agent handoff

​One-click setup

​Overview

​Prerequisites

​Endpoint URL

​Authentication

​Payload Format

​Manual setup steps

​Working cURL Example

​Agent handoff

One-click setup

Overview

Prerequisites

Endpoint URL

Authentication

Payload Format

Manual setup steps

Working cURL Example

Agent handoff