tracing_config
field of any listener object. Properly configured, the Sidecar will send spans to the trace collector server with information on the request and its path through the mesh.tracing_enabled
bool
false
tracing_address
string
"localhost"
tracing_port
int
9411
tracing_collector_endpoint
string
/api/v1/spans
tracing_use_tls
bool
false
tracing_ca_cert_path
string
./certs/egress_intermediate.crt
tracing_cert_path
string
./certs/egress_localhost.crt
tracing_key_path
string
./certs/egress_localhost.key
ingress
boolean
true
request_headers_for_tags
[]string
null
ingress
determines the operation_name
value in the Envoy HTTP connection manager tracing configuration. By default in both Grey Matter and Envoy, ingress
is true and "operation_name": "INGRESS"
. If ingress
is set to false
, operation_name
will be "operation_name": "EGRESS"
. This determines the traffic direction of the trace.null
, and no tags are configured. If values are configured, a tag is created if the value is present in the requests headers, with the header name used as the tag name, and the header value used as the tag value in a span.TRACING_*
environment variables set.tracing_config
on the Grey Matter listener for the desired service configures the mesh to start sending traces to this server.tracing_config
set will look something like the following: