ConstTrace context headers will not be set because the request is a cross-origin request.
Trace context headers will not be set because they are disabled via configuration flag.
Trace context headers will not be set because they are excluded via block-list configuration flag.
The traceparent header already existed on the request and was set by a different party.
Indicator for our sent event that the trace.id is not generated, but comes from the server
Trace context headers will be set because they are either cross-origin or non-http, and are included via allow-list configuration flag.
The traceparent header already existed on the request but is invalid according to the spec
The tracestate header was not set because it would have exceeded the maximum allowed length
The tracestate header was not set due to missing required values for construction
Trace context headers will not be set because the request URL protocol is not http or https. Use the allow-list configuration flag to include such requests nevertheless.
Trace id can't be set because neither we generated on, nor we got one from the server
Trace context headers will be set because the request is a same-origin request with ah http or https protocol.