Open source


otelcol.receiver.zipkin accepts Zipkin-formatted traces over the network and forwards it to other otelcol.* components.

NOTE: otelcol.receiver.zipkin is a wrapper over the upstream OpenTelemetry Collector zipkin receiver. Bug reports or feature requests will be redirected to the upstream repository, if necessary.

Multiple otelcol.receiver.zipkin components can be specified by giving them different labels.


otelcol.receiver.zipkin "LABEL" {
  output {
    traces = [...]


otelcol.receiver.zipkin supports the following arguments:

parse_string_tagsboolParse string tags and binary annotations into non-string types.falseno
endpointstringhost:port to listen for traffic on.""no
max_request_body_sizestringMaximum request body size the HTTP server will allow. No limit when
include_metadatabooleanPropagate incoming connection metadata to downstream

If parse_string_tags is true, string tags and binary annotations are converted to int, bool, and float if possible. String tags and binary annotations that cannot be converted remain unchanged.


The following blocks are supported inside the definition of otelcol.receiver.zipkin:

tlstlsConfigures TLS for the HTTP
corscorsConfigures CORS for the HTTP
outputoutputConfigures where to send received traces.yes

The > symbol indicates deeper levels of nesting. For example, grpc > tls refers to a tls block defined inside a grpc block.

tls block

The tls block configures TLS settings used for a server. If the tls block isn’t provided, TLS won’t be used for connections to the server.

The following arguments are supported:

ca_filestringPath to the CA
cert_filestringPath to the TLS
key_filestringPath to the TLS certificate
min_versionstringMinimum acceptable TLS version for connections."TLS 1.2"no
max_versionstringMaximum acceptable TLS version for connections."TLS 1.3"no
reload_intervaldurationFrequency to reload the
client_ca_filestringPath to the CA file used to authenticate client

cors block

The cors block configures CORS settings for an HTTP server.

The following arguments are supported:

allowed_originslist(string)Allowed values for the Origin
allowed_headerslist(string)Accepted headers from CORS requests.["X-Requested-With"]no
max_agenumberConfigures the Access-Control-Max-Age response

The allowed_headers argument specifies which headers are acceptable from a CORS request. The following headers are always implicitly allowed:

  • Accept
  • Accept-Language
  • Content-Type
  • Content-Language

If allowed_headers includes "*", all headers are permitted.

output block

The output block configures a set of components to forward resulting telemetry data to.

The following arguments are supported:

metricslist(otelcol.Consumer)List of consumers to send metrics to.[]no
logslist(otelcol.Consumer)List of consumers to send logs to.[]no
traceslist(otelcol.Consumer)List of consumers to send traces to.[]no

The output block must be specified, but all of its arguments are optional. By default, telemetry data is dropped. To send telemetry data to other components, configure the metrics, logs, and traces arguments accordingly.

Exported fields

otelcol.receiver.zipkin does not export any fields.

Component health

otelcol.receiver.zipkin is only reported as unhealthy if given an invalid configuration.

Debug information

otelcol.receiver.zipkin does not expose any component-specific debug information.


This example forwards received traces through a batch processor before finally sending it to an OTLP-capable endpoint:

otelcol.receiver.zipkin "default" {
  output {
    traces = [otelcol.processor.batch.default.input]

otelcol.processor.batch "default" {
  output {
    metrics = [otelcol.exporter.otlp.default.input]
    logs    = [otelcol.exporter.otlp.default.input]
    traces  = [otelcol.exporter.otlp.default.input]

otelcol.exporter.otlp "default" {
  client {
    endpoint = env("OTLP_ENDPOINT")