Demonstrate Propagation of Additional Trace Identifiers in Traces and Spans #10
Description
Is your feature request related to a problem? Please describe
We need to demonstrate the propagation of additional trace identifiers such as x-request-id, tenant-id, and a custom identifier (e.g., originating-bi-id) across traces and spans. This will help ensure that these critical identifiers are correctly passed along the system, allowing for better traceability and easier debugging in a distributed environment.
Describe the solution you'd like
Implement functionality to propagate the following trace identifiers across relevant traces and spans:
x-request-idtenant-id- Custom identifier, such as
originating-bi-id
Ensure that Identifiers can be propagated with auto instrumentation, without change the source code.
These identifiers should be included in the trace context and visible in the tracing backend (e.g., Jaeger). This will ensure that requests can be traced accurately across different services and that relevant context is maintained throughout the request lifecycle.
The solution should:
- Demonstrate the propagation of these identifiers through the system.
- Ensure that the identifiers are visible in the spans and traces in the tracing backend.
- Provide test cases to validate that these identifiers are being correctly propagated.
Describe alternatives you've considered
No response
Additional information
No response