Zipkin tracer

This documentation is for the Envoy v3 API.

As of Envoy v1.18 the v2 API has been removed and is no longer supported.

If you are upgrading from v2 API config you may wish to view the v2 API documentation:


[config.trace.v3.ZipkinConfig proto]

Configuration for the Zipkin tracer.

This extension may be referenced by the qualified name envoy.tracers.zipkin


This extension is intended to be robust against untrusted downstream traffic. It assumes that the upstream is trusted.


This extension extends and can be used with the following extension category:

  "collector_cluster": "...",
  "collector_endpoint": "...",
  "trace_id_128bit": "...",
  "shared_span_context": "{...}",
  "collector_endpoint_version": "...",
  "collector_hostname": "..."

(string, REQUIRED) The cluster manager cluster that hosts the Zipkin collectors.


(string, REQUIRED) The API endpoint of the Zipkin service where the spans will be sent. When using a standard Zipkin installation, the API endpoint is typically /api/v1/spans, which is the default value.


(bool) Determines whether a 128bit trace id will be used when creating a new trace instance. The default value is false, which will result in a 64 bit trace id being used.


(BoolValue) Determines whether client and server spans will share the same span context. The default value is true.


(config.trace.v3.ZipkinConfig.CollectorEndpointVersion) Determines the selected collector endpoint version. By default, the HTTP_JSON_V1 will be used.


(string) Optional hostname to use when sending spans to the collector_cluster. Useful for collectors that require a specific hostname. Defaults to collector_cluster above.

Enum config.trace.v3.ZipkinConfig.CollectorEndpointVersion

[config.trace.v3.ZipkinConfig.CollectorEndpointVersion proto]

Available Zipkin collector endpoint versions.


(DEFAULT) ⁣Zipkin API v1, JSON over HTTP.


⁣Zipkin API v2, JSON over HTTP.


⁣Zipkin API v2, protobuf over HTTP.