You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This option allows some control on how the APM agent handles W3C trace-context headers on incoming requests.
1188
+
By default, the `traceparent` and `tracestate` headers are used per W3C spec for distributed tracing.
1189
+
However, in certain cases it can be helpful to *not* use the incoming `traceparent` header.
1190
+
Some example use cases:
1191
+
1192
+
- An Elastic-monitored service is receiving requests with `traceparent` headers from *unmonitored* services.
1193
+
- An Elastic-monitored service is publicly exposed, and does not want tracing data (trace-ids, sampling decisions) to possibly be spoofed by user requests.
1194
+
1195
+
Valid values are:
1196
+
1197
+
- `'continue'`: The default behavior. An incoming `traceparent` value is used to continue the trace and determine the sampling decision.
1198
+
- `'restart'`: Always ignores the `traceparent` header of incoming requests.
1199
+
A new trace-id will be generated and the sampling decision will be made based on <<config-transaction-sample-rate,`transaction_sample_rate`>>.
1200
+
A *span link* will be made to the incoming traceparent.
1201
+
- `'restart_external'`: If an incoming request includes the `es` vendor flag in `tracestate`, then any 'traceparent' will be considered internal and will be handled as described for `'continue'` above.
1202
+
Otherwise, any `'traceparent'` is considered external and will be handled as described for `'restart'` above.
1203
+
1204
+
Starting with Elastic Observability 8.2, span links will be visible in trace
0 commit comments