Initial W3C Traceparent and otel integration.#1800
Merged
Conversation
adamkorynta
requested changes
Jul 1, 2026
MikeNeilson
commented
Jul 1, 2026
MikeNeilson
left a comment
MikeNeilson
left a comment
Contributor
Author
There was a problem hiding this comment.
Thanks. Good things to fix.
…and compose files.
MikeNeilson
force-pushed
the
task/handle-mdc
branch
from
d50a983 to
131d57c
Compare
adamkorynta
approved these changes
Jul 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Setup appropriate Servlet Filter and baseline OpenTelemetry setup to handle parsing and propagation of the W3C TraceParent header.
NOTE: intentionally not setting up the otel agent at this time. Nor am I'm worried about thread propagation (I'm certain that's not behaving correctly). This is intended to be the most minimal change to support and have the w3c trace parent header and have the trace id and span id values. And setting up some basic integration with open telemetry.
Related Issue
Closes #1697
Validation
Manually verified that a context is either generated, or propagated (e.g. from user provided context) if valid.
Added specific traceparent to integration test for manual verification.
Checklist