From f3b6d18352a3370fed6d251671a86977666c11d8 Mon Sep 17 00:00:00 2001 From: Yifan Yang Date: Wed, 30 Oct 2024 21:58:53 +0800 Subject: [PATCH] docs for PR caddyserver/caddy#6646 (#429) Signed-off-by: YifanYang6 --- src/docs/markdown/caddyfile/directives/tracing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/docs/markdown/caddyfile/directives/tracing.md b/src/docs/markdown/caddyfile/directives/tracing.md index 95cfb7e..c7b6a2f 100644 --- a/src/docs/markdown/caddyfile/directives/tracing.md +++ b/src/docs/markdown/caddyfile/directives/tracing.md @@ -10,7 +10,7 @@ When enabled, it will propagate an existing trace context or initialize a new on It uses [gRPC](https://github.com/grpc/) as an exporter protocol and W3C [tracecontext](https://www.w3.org/TR/trace-context/) and [baggage](https://www.w3.org/TR/baggage/) as propagators. -The trace ID is added to [access logs](/docs/caddyfile/directives/log) as the standard `traceID` field. Additionally, the `{http.vars.trace_id}` placeholder is made available, for example to add the ID to a (`request_header`)[request_header] to pass it to your app. +The trace ID and span ID are added to [access logs](/docs/caddyfile/directives/log) as the standard `traceID` and `spanID` fields. Additionally, the `{http.vars.trace_id}` and `{http.vars.span_id}` placeholders are available; for example, you can use them in a [`request_header`](request_header) to pass the IDs to your app.