Tracing

The tracing configuration specifies global settings for the HTTP tracer used by Envoy. The configuration is defined on the server’s top level configuration. Envoy may support other tracers in the future, but right now the HTTP tracer is the only one supported.

  1. {
  2.   "http": {
  3.     "driver": "{...}"
  4.   }
  5. }

http

(optional, object) Provides configuration for the HTTP tracer.

driver

(optional, object) Provides the driver that handles trace and span creation.

Currently LightStep and Zipkin drivers are supported.

LightStep driver

  1. {
  2.   "type": "lightstep",
  3.   "config": {
  4.     "access_token_file": "...",
  5.     "collector_cluster": "..."
  6.   }
  7. }

access_token_file

(required, string) File containing the access token to the LightStep API.

collector_cluster

(required, string) The cluster manager cluster that hosts the LightStep collectors.

Zipkin driver

  1. {
  2.   "type": "zipkin",
  3.   "config": {
  4.     "collector_cluster": "...",
  5.     "collector_endpoint": "..."
  6.   }
  7. }

collector_cluster

(required, string) The cluster manager cluster that hosts the Zipkin collectors. Note that the Zipkin cluster must be defined under clusters in the cluster manager configuration section.

collector_endpoint

(optional, string) 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.