13.1.4 List of Trace Headers

When you want to trace the transaction from end-to-end, set oracle.tmm.PropagateTraceHeaders to true. This propagates the trace headers for all incoming and outgoing requests.

The following table lists a few of the trace headers that are propagated.

Name of the headers	Description
x-request-id	All applications must propagate this header. This header is included in access log statements and it is used for consistent trace sampling and log sampling decisions in Istio.
oracle-tmm-tx-token authorization refresh-token oracle-tmm-authz-token	These MicroTx-specific headers must be propagated for running the MicroTx API calls from the library.
end-user	This header is specific to the application and you can forward this header.
x-ot-span-context	Propagate this header if you are using Lightstep tracing in Istio. See https://istio.io/latest/docs/tasks/observability/distributed-tracing/lightstep/.
x-datadog-trace-id x-datadog-parent-id x-datadog-sampling-priority	Propagate these headers if you are using Datadog tracing.
traceparent tracestate	These are W3C trace context headers. They are compatible with OpenCensus Agent and Stackdriver configurations for Istio.
x-cloud-trace-context	This is a Cloud Trace context header. It is compatible with OpenCensus Agent and Stackdriver configurations for Istio.
grpc-trace-bin	This is a gRPC binary trace context header. It is compatible with OpenCensus Agent and Stackdriver configurations for Istio.
x-b3-traceid x-b3-spanid x-b3-parentspanid x-b3-sampled x-b3-flags	These are B3 trace context headers. They are compatible with Zipkin, OpenCensus Agent, and Stackdriver configurations for Istio.