Skip to main content

Documentation Index

Fetch the complete documentation index at: https://otel.fyi/llms.txt

Use this file to discover all available pages before exploring further.

Googlecloudpubsubpush Receiver

Status Maintainers: @axw, @constanca-m Source: opentelemetry-collector-contrib

Supported Telemetry

Logs

Overview

NOTE: Refer to Difference to the current google pub sub receiver if you don’t know which receiver to use or just want to understand the differences.
The googlecloudpubsubpush receiver ingests OpenTelemetry data through Google Cloud Pub/Sub push subscriptions, supporting two primary data ingestion patterns:
  • Direct Log Ingestion: Processes Pub/Sub messages containing log data directly.
  • GCS Event Processing: Handles Pub/Sub notifications for new files in Google Cloud Storage.
All received data is parsed into OpenTelemetry format using configurable encoding extensions, enabling flexible and near real-time telemetry collection from multiple Google Cloud sources.

Example configuration

receivers:
  googlecloudpubsubpush:
    endpoint: :8080
    encoding: google_cloud_logentry_encoding

extensions:
  google_cloud_logentry_encoding:

Difference to the current google pub sub receiver

The main difference between the current googlecloudpubsub receiver and the proposed new receiver lies in how they receive messages from Google Pub/Sub: pull vs. push subscriptions. The table below summarizes their differences:
Componentgooglecloudpubsubgooglecloudpubsubpush (this receiver)
SubscriptionPullPush
Data FlowThe receiver polls Pub/Sub to ask for new messages.Pub/Sub actively pushes new messages to the receiver.
InitiatorReceiverPub/Sub
You can read more about Pull/Push subscriptions in the official documentation.

Attributes

Attribute NameDescriptionTypeValues
gcp.gcs.bucket.nameBucket name.string
http.response.status_codeHTTP response status code.int

Configuration

Example Configuration

googlecloudpubsubpush:
  encoding: test

googlecloudpubsubpush/empty_encoding:

googlecloudpubsubpush/misformatted_endpoint:
  encoding: test
  endpoint: invalid_endpoint

Last generated: 2026-04-20