Distributed Tracing Working Group - Activity in 2025
No matches.
Past meetings
Participants
-
1 participant joined.
-
Sanjana Bonneau-Desai (1Password) joined.
-
-
1 organization joined.
-
1Password joined.
-
Past meetings
Participants
-
2 participants joined.
-
Zachary Montoya (Datadog) joined.
-
Brian Marks (Datadog) joined.
-
-
2 participants left.
-
Rohit Kapur (Datadog) left.
-
Alexander Costas (Datadog) left.
-
GitHub
w3c/trace-context-protocols-registry
-
2 issues opened.
-
Hacked and bugged w3c/trace-context-protocols-registry#17, by @blayzesmom10-lab.
-
Drop registry entries for Binary, MQTT, and AMQP w3c/trace-context-protocols-registry#16, by @plehegar.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
chore: update Slack link w3c/trace-context-protocols-registry#15, by @basti1302.
-
-
1 pull request merged.
-
chore: update Slack link w3c/trace-context-protocols-registry#15.
-
w3c/trace-context
-
1 pull request opened.
-
Add Datadog W3C trace context docs w3c/trace-context#578, by @bm1549.
-
-
1 pull request merged.
-
Add Datadog W3C trace context docs w3c/trace-context#578.
-
-
1 pull request received 1 new comment.
Past meetings
GitHub
w3c/trace-context
-
1 pull request merged.
-
Use server-timing for trace context response w3c/trace-context#560.
-
Past meetings
Participants
-
2 participants joined.
-
narendra reddy sanikommu (NVIDIA) joined.
-
AMIT KUMAR PADHY (Adobe) joined.
-
-
2 organizations joined.
-
NVIDIA joined.
-
Adobe joined.
-
GitHub
w3c/trace-context
-
1 pull request received 3 new comments.
-
Use server-timing for trace context response w3c/trace-context#560 (3 comments by @balajikris, @johnbley)
-
Lifecycle
-
1 charter started.
-
Chartered until 21 August 2027.
-
Past meetings
Participants
-
1 participant left.
-
J. Kalyana Sundaram (Microsoft Corporation) left.
-
Past meetings
GitHub
w3c/trace-response-headers
-
1 issue opened.
-
Archive repository? w3c/trace-response-headers#1, by @tidoust.
-
w3c/trace-interchange-format
-
1 issue opened.
-
Archive repository? w3c/trace-interchange-format#2, by @tidoust.
-
w3c/trace-context-protocols-registry
-
1 issue received 1 new comment.
-
w3c/trace-context-protocols-registry#4 (1 comment by @KalleOlaviNiemitalo)
-
Past meetings
GitHub
w3c/trace-context
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Fix build badge w3c/trace-context#577, by @martincostello.
-
-
1 pull request merged.
-
Fix build badge w3c/trace-context#577.
-
-
1 pull request received 2 new comments.
w3c/baggage
-
2 issues closed.
-
2 pull requests merged.
-
clarify encoding rules for property values w3c/baggage#148.
-
-
1 pull request received 1 new comment.
-
Clarify that the behavior for handling invalid baggage string values is undefined w3c/baggage#147 (1 comment by @balajikris)
-
Lifecycle
Past meetings
Participants
-
1 participant joined.
-
Sateesh Mamidala (Capital One Discover Network) joined.
-
-
1 organization joined.
-
Capital One Discover Network joined.
-
GitHub
w3c/baggage
-
1 issue opened.
-
1 issue received 3 new comments.
-
Python: Audit the Otel implementation of Baggage w3c/baggage#140 (3 comments by @dyladan, @yurishkuro)
-
Past meetings
Participants
-
1 participant joined.
-
John Bley (Cisco) joined.
-
-
1 organization joined.
-
Cisco joined.
-
GitHub
w3c/trace-context
-
1 issue opened.
-
Contradiction in TraceState format description w3c/trace-context#576, by @xrfang.
-
-
1 issue received 1 new comment.
-
1 pull request received 5 new comments.
w3c/baggage
-
1 issue closed.
-
1 issue received 1 new comment.
-
Java: Audit the Otel implementation of Baggage using Baggage Test Suite w3c/baggage#138 (1 comment by @SergeyKanzhelev)
-
Past meetings
GitHub
w3c/baggage
-
1 issue received 2 new comments.
-
GoLang: Audit the Otel implementation of Baggage w3c/baggage#141 (2 comments by @jcopi, @yurishkuro)
-
Past meetings
GitHub
w3c/baggage
-
1 issue received 1 new comment.
-
Discussion: Should we drop the requirement to percent-encode values of list-members w3c/baggage#145 (1 comment by @basti1302)
-
-
3 pull requests opened.
-
clarify encoding rules for property values w3c/baggage#148, by @basti1302.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/baggage#146, by @deniak.
-
-
1 pull request merged.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/baggage#146.
-
-
1 pull request closed.
-
3 pull requests received 6 new comments.
-
Clarify that the behavior for handling invalid baggage string values is undefined w3c/baggage#147 (4 comments by @balajikris, @basti1302, @yurishkuro)
-
Clarify that the behavior for handling invalid baggage string values is undefined w3c/baggage#144 (1 comment by @balajikris)
-
w3c/trace-context
-
1 issue closed.
-
Question about tracecontext in load-balancer scenarios w3c/trace-context#575.
-
-
1 issue received 1 new comment.
-
Question about tracecontext in load-balancer scenarios w3c/trace-context#575 (1 comment by @balajikris)
-
Past meetings
Participants
-
1 chair stepped down.
-
J. Kalyana Sundaram stepped down as a chair.
-
-
1 participant joined.
-
Balaji Krishnan (Microsoft Corporation) joined.
-
GitHub
w3c/trace-context
-
1 issue received 2 new comments.
-
Question about tracecontext in load-balancer scenarios w3c/trace-context#575 (2 comments by @kalyanaj, @SergeyKanzhelev)
-
w3c/baggage
-
4 issues received 4 new comments.
-
Clarify how compliant implementations should handle invalid baggage entries w3c/baggage#137 (1 comment by @SergeyKanzhelev)
-
Discussion: Should we drop the requirement to percent-encode values of list-members w3c/baggage#145 (1 comment by @SergeyKanzhelev)
-
.NET: Audit the OpenTelemetry implementation of Baggage using Baggage test suite w3c/baggage#139 (1 comment by @kalyanaj)
-