Caution

Grafana Agent has reached End-of-Life (EOL) on November 1, 2025. Agent is no longer receiving vendor support and will no longer receive security or bug fixes. Current users of Agent Static mode, Agent Flow mode, and Agent Operator should proceed with migrating to Grafana Alloy. If you have already migrated to Alloy, no further action is required. Read more about why we recommend migrating to Grafana Alloy.

Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.

Documentationbreadcrumb arrow Grafana Agentbreadcrumb arrow Flow modebreadcrumb arrow Referencebreadcrumb arrow Componentsbreadcrumb arrow otelcol.receiver.zipkin
Open source

otelcol.receiver.zipkin

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.

Usage

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

Arguments

otelcol.receiver.zipkin supports the following arguments:

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

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.

Blocks

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

HierarchyBlockDescriptionRequired
tlstlsConfigures TLS for the HTTP server.no
corscorsConfigures CORS for the HTTP server.no
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:

NameTypeDescriptionDefaultRequired
ca_pemstringCA PEM-encoded text to validate the server with.no
ca_filestringPath to the CA file.no
cert_pemstringCertificate PEM-encoded text for client authentication.no
cert_filestringPath to the TLS certificate.no
key_pemsecretKey PEM-encoded text for client authentication.no
key_filestringPath to the TLS certificate key.no
min_versionstringMinimum acceptable TLS version for connections."TLS 1.2"no
max_versionstringMaximum acceptable TLS version for connections."TLS 1.3"no
reload_intervaldurationThe duration after which the certificate will be reloaded."0s"no
insecurebooleanDisables TLS when connecting to the configured server.no
insecure_skip_verifybooleanIgnores insecure server TLS certificates.no
server_namestringVerifies the hostname of server certificates when set.no

If the server doesn’t support TLS, the tls block must be provided with the insecure argument set to true. To disable tls for connections to the server, set the insecure argument to true.

If reload_interval is set to "0s", the certificate will never be reloaded.

The following pairs of arguments are mutually exclusive and cannot both be set simultaneously:

  • ca_pem and ca_file
  • cert_pem and cert_file
  • key_pem and key_file

cors block

The cors block configures CORS settings for an HTTP server.

The following arguments are supported:

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

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:

NameTypeDescriptionDefaultRequired
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.

Example

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

Alloy 
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")
  }
}