Integration

Google Cloud

Cloud Logging from Cloud Run, GKE, Cloud Functions, App Engine, Compute Engine and audit logs through a Pub/Sub push subscription.

Category: Cloud
How data is sent: The service sends its logs (HTTPS, nothing to install)
Status: Beta

How it works#

Answer a few questions. They only fill in the setup steps. Logthread never signs in to your Google Cloud account.
Create a Pub/Sub sink in your project. The next page shows the endpoint with this connector's ingest key filled in. There is nothing to install.
Data arrives. Google Cloud sends the logs over HTTPS to ingest.logthread.com with this connector's key. The connection page shows what has arrived and turns Active with the first record.

What you answer#

Question	Answer	Notes
Project id	Text	The Google Cloud project id, for example my-shop-prod (not the display name).
Log filter (optional)	Text	A Cloud Logging filter for the sink, for example resource.type="cloud_run_revision". Empty sends every log.
Service name (optional)	Text	Every record gets this service name unless it names its own. Leave empty to name services automatically.

Setup#

These are the steps for the default answers. In the app, they follow your answers, and the connector's ingest key replaces YOUR_INGEST_KEY.

Step 1. Create the topic and the push subscription. With the gcloud CLI signed in to the project. The subscription pushes every message to Logthread over HTTPS; the key in the address is this connector's ingest key, and nothing else is needed.

gcloud pubsub topics create logthread-logs --project=my-shop-prod
gcloud pubsub subscriptions create logthread-logs --topic=logthread-logs \
  --push-endpoint='https://ingest.logthread.com/v1/integrations/pubsub?key=YOUR_INGEST_KEY' --ack-deadline=30 --project=my-shop-prod

Step 2. Route Cloud Logging to the topic. The sink sends matching log entries to the topic as they are written. Without a filter it sends every log in the project; the filter uses Cloud Logging query syntax, for example resource.type="cloud_run_revision" or severity>=WARNING.

gcloud logging sinks create logthread \
  pubsub.googleapis.com/projects/my-shop-prod/topics/logthread-logs --project=my-shop-prod
# Let the sink publish to the topic (it writes as its own service account):
gcloud pubsub topics add-iam-policy-binding logthread-logs --project=my-shop-prod \
  --member="$(gcloud logging sinks describe logthread --project=my-shop-prod --format='value(writerIdentity)')" --role=roles/pubsub.publisher

Step 3. Wait for data. Entries arrive within seconds. Cloud Run, Cloud Functions, GKE containers and App Engine become their own services, named as in Google Cloud; everything else is named after its resource type. In the console, the subscription's Metrics tab shows push errors if any.

Check that it works#

The connection page under Integrations counts the records sent with the connector's key and turns Active with the first one.

Then add#

Each is one click on the connection page and opens with your data, so you can check it before saving.

Dashboard: Google Cloud: Logs by severity and service, Cloud Run requests by status and latency, audit activity and failing paths from Cloud Logging through Pub/Sub.
Alert: Google Cloud errors: logthread.source:gcp_pubsub severity:(error|fatal), at least 10 in 10 minutes
Alert: Audit log permission denied: logthread.source:gcp_pubsub gcp.audit.status_code:7, at least 1 in 10 minutes

Set it up under Integrations in the app, or from an AI agent with MCP (add_integration). All integrations: Integrations guide. Next: find what it sends in Explore and live tail.