Pulsar Receiver
contrib
Maintainers: @dao-jun
Source: opentelemetry-collector-contrib
Supported Telemetry
Overview
Getting Started
The following settings can be optionally configured:endpoint(default = pulsar://localhost:6650): The url of pulsar cluster.topic(default = otlp_spans for traces, otlp_metrics for metrics, otlp_logs for logs): The name of the pulsar topic to consume from.encoding(default = otlp_proto): The encoding of the payload sent to pulsar. Available encodings:otlp_proto: the payload is deserialized toExportTraceServiceRequest.jaeger_proto: the payload is deserialized to a single Jaeger protoSpan.jaeger_json: the payload is deserialized to a single Jaeger JSON Span usingjsonpb.zipkin_proto: the payload is deserialized into a list of Zipkin proto spans.zipkin_json: the payload is deserialized into a list of Zipkin V2 JSON spans.zipkin_thrift: the payload is deserialized into a list of Zipkin Thrift spans.
consumer_name: specifies the consumer name.authtlscert_file:key_file:
tokentoken
oauth2issuer_url:client_id:audience:scope:private_key: Path to the private client credentials json file. Must containtype,client_id,client_secretandissuer_urlfields.
athenzprovider_domain:tenant_domain:tenant_service:private_key:key_id:principal_header:zts_url:
subscription(default = otlp_subscription): the subscription name of consumer.tls_trust_certs_file_path: path to the CA cert. For a client this verifies the server certificate. Should only be used ifinsecureis set to true.tls_allow_insecure_connection: configure whether the Pulsar client accept untrusted TLS certificate from broker (default: false)
Configuration
Example Configuration
Last generated: 2026-04-13