Distributed Tracing Working Group - Activity in 2024
No matches.
Past meetings
Participants
-
2 participants left.
-
Yash Shah (Microsoft Corporation) left.
-
Jon Bringhurst (Microsoft Corporation) left.
-
GitHub
w3c/trace-context
-
1 issue closed.
-
Trace Context Extensibility w3c/trace-context#573.
-
-
2 issues received 2 new comments.
-
Revisit header name -- Server-Timing vs. traceresponse w3c/trace-context#556 (1 comment by @gredler)
Past meetings
Participants
-
1 participant left.
-
Kit Freddura (Datadog) left.
-
GitHub
w3c/baggage
-
1 issue opened.
-
2 issues received 7 new comments.
-
Java: Audit the Otel implementation of Baggage using Baggage Test Suite w3c/baggage#138 (6 comments by @basti1302, @dyladan, @yurishkuro)
-
Discussion: Should we drop the requirement to percent-encode values of list-members w3c/baggage#145 (1 comment by @basti1302)
-
-
2 pull requests opened.
-
fix: replace two instances of "Context" by "Baggage" w3c/baggage#143, by @basti1302.
-
1 pull request merged.
-
fix: replace two instances of "Context" by "Baggage" w3c/baggage#143.
-
-
1 pull request received 1 new comment.
-
Clarify that the behavior for handling invalid baggage string values is undefined w3c/baggage#144 (1 comment by @SergeyKanzhelev)
-
w3c/trace-context
-
1 issue opened.
-
Question about tracecontext in load-balancer scenarios w3c/trace-context#575, by @kalyanaj.
-
-
2 issues received 2 new comments.
-
Question about tracecontext in load-balancer scenarios w3c/trace-context#575 (1 comment by @basti1302)
-
-
1 pull request merged.
-
Adds a pure javascript implementation of trace contexts w3c/trace-context#571.
-
-
1 pull request reopened.
-
Adds a pure javascript implementation of trace contexts w3c/trace-context#571, by @dyladan.
-
Past meetings
GitHub
w3c/baggage
-
2 issues received 2 new comments.
-
Clarify how compliant implementations should handle invalid baggage entries w3c/baggage#137 (1 comment by @kalyanaj)
Past meetings
Participants
-
2 participants joined.
-
Kit Freddura (Datadog) joined.
-
Rohit Kapur (Datadog) joined.
-
GitHub
w3c/trace-context
-
1 issue closed.
-
request for clarification re size of parent-id w3c/trace-context#574.
-
-
2 issues received 5 new comments.
-
request for clarification re size of parent-id w3c/trace-context#574 (3 comments by @basti1302, @hepabolu)
-
w3c/baggage
-
5 issues opened.
-
Audit baggage test suite w3c/baggage#142, by @kalyanaj.
-
GoLang: Audit the Otel implementation of Baggage w3c/baggage#141, by @kalyanaj.
-
Python: Audit the Otel implementation of Baggage w3c/baggage#140, by @kalyanaj.
-
Java: Audit the Otel implementation of Baggage using Baggage Test Suite w3c/baggage#138, by @kalyanaj.
-
Past meetings
Participants
-
1 participant joined.
-
Alexander Costas (Datadog) joined.
-
-
1 organization joined.
-
Datadog joined.
-
GitHub
w3c/trace-context
-
1 issue opened.
-
request for clarification re size of parent-id w3c/trace-context#574, by @helmavdl.
-
-
3 issues received 5 new comments.
-
request for clarification re size of parent-id w3c/trace-context#574 (3 comments by @basti1302, @helmavdl)
-
Proposal: Add a "propagation-only-parent" flag to be set to true if parents is a no-tracing service w3c/trace-context#550 (1 comment by @bogdandrutu)
-
w3c/baggage
-
1 issue opened.
-
Clarify how compliant implementations should handle invalid baggage entries w3c/baggage#137, by @lachmatt.
-
-
1 issue received 2 new comments.
-
Clarify how compliant implementations should handle invalid baggage entries w3c/baggage#137 (2 comments by @lachmatt, @xiang17)
-
TR publications
-
2 documents published.
-
Propagation format for distributed context: Baggage published as a Candidate Recommendation Snapshot. History of Propagation format for distributed context: Baggage
-
Propagation format for distributed context: Baggage published as a Working Draft. History of Propagation format for distributed context: Baggage
-
Past meetings
GitHub
w3c/baggage
-
1 issue opened.
-
Clarification regarding baggage list-member value w3c/baggage#135, by @lachmatt.
-
-
1 issue closed.
-
Wide review w3c/baggage#91.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Implementation report and CR tweaks w3c/baggage#136, by @plehegar.
-
-
1 pull request merged.
-
Implementation report and CR tweaks w3c/baggage#136.
-
-
1 pull request closed.
-
Remove all markdown includes w3c/baggage#132.
-
-
1 pull request received 2 new comments.
w3c/trace-context
-
1 issue opened.
-
Trace Context Extensibility w3c/trace-context#573, by @dyladan.
-
-
1 issue received 6 new comments.
-
4 pull requests closed.
-
Remove data include for overview w3c/trace-context#565.
-
Remove data include for request header format w3c/trace-context#566.
-
Remove data include for abstract w3c/trace-context#563.
-
Remove data include for sotd w3c/trace-context#564.
-
w3c/trace-context-protocols-registry
-
1 pull request opened.
-
Added a column for specification status w3c/trace-context-protocols-registry#14, by @kalyanaj.
-
-
1 pull request merged.
-
Added a column for specification status w3c/trace-context-protocols-registry#14.
-
TR publications
-
1 document published.
-
Propagation format for distributed context: Baggage published as a Working Draft. History of Propagation format for distributed context: Baggage
-
Past meetings
GitHub
w3c/trace-context
-
1 issue opened.
-
Can Traceresponse enable parent-child relationship between browser and server spans? w3c/trace-context#572, by @scheler.
-
w3c/baggage
-
1 issue opened.
-
Extend parse tests with more use cases w3c/baggage#134, by @pellared.
-
-
1 issue closed.
-
We need to document the reasoning for the supported character range w3c/baggage#128.
-
-
1 pull request merged.
-
Add notes explaining missing unicode character support w3c/baggage#133.
-
TR publications
-
2 documents published.
-
Trace Context Level 2 published as a Candidate Recommendation Draft. History of Trace Context Level 2
-
Propagation format for distributed context: Baggage published as a Working Draft. History of Propagation format for distributed context: Baggage
-
Past meetings
GitHub
w3c/trace-context
-
1 issue opened.
-
Remove all markdown includes w3c/trace-context#562, by @dyladan.
-
-
2 issues received 4 new comments.
-
Autopublishing level2/Level3 specs need to work with multiple markdown files w3c/trace-context#545 (2 comments by @plehegar)
-
-
9 pull requests opened.
-
Adds a pure javascript implementation of trace contexts w3c/trace-context#571, by @maraisr.
-
Level 2 autopublish.-checkoutv4 w3c/trace-context#570, by @plehegar.
-
Fixed short-name for autopublish w3c/trace-context#569, by @plehegar.
-
Level 2 autopublish w3c/trace-context#568, by @plehegar.
-
auto-publish for Level 2 w3c/trace-context#567, by @plehegar.
-
Remove data include for request header format w3c/trace-context#566, by @dyladan.
-
Remove data include for overview w3c/trace-context#565, by @dyladan.
-
Remove data include for sotd w3c/trace-context#564, by @dyladan.
-
Remove data include for abstract w3c/trace-context#563, by @dyladan.
-
-
3 pull requests merged.
-
Level 2 autopublish.-checkoutv4 w3c/trace-context#570.
-
Fixed short-name for autopublish w3c/trace-context#569.
-
Level 2 autopublish w3c/trace-context#568.
-
-
1 pull request closed.
-
auto-publish for Level 2 w3c/trace-context#567.
-
-
3 pull requests received 6 new comments.
-
Use server-timing for trace context response w3c/trace-context#560 (4 comments by @basti1302, @dyladan)
-
Adds a pure javascript implementation of trace contexts w3c/trace-context#571 (1 comment by @w3cbot)
-
w3c/baggage
-
1 issue opened.
-
Test harness to show handling of invalid inputs w3c/baggage#131, by @yurishkuro.
-
-
2 pull requests opened.
-
Add notes explaining missing unicode character support w3c/baggage#133, by @dyladan.
-
Remove all markdown includes w3c/baggage#132, by @dyladan.
-
-
1 pull request merged.
-
Use the term code point where character may be ambiguous w3c/baggage#130.
-
-
1 pull request closed.
-
Don't merge w3c/baggage#121.
-
-
3 pull requests received 9 new comments.
-
Use the term code point where character may be ambiguous w3c/baggage#130 (6 comments by @dyladan, @kalyanaj, @SergeyKanzhelev)
-
TR publications
-
1 document published.
-
Propagation format for distributed context: Baggage published as a Working Draft. History of Propagation format for distributed context: Baggage
-
Past meetings
GitHub
w3c/trace-context
-
1 issue opened.
-
Server-timing names w3c/trace-context#561, by @SergeyKanzhelev.
-
-
2 issues received 8 new comments.
-
Revisit header name -- Server-Timing vs. traceresponse w3c/trace-context#556 (4 comments by @basti1302, @jpkrohling, @kalyanaj, @yurishkuro)
-
1 pull request opened.
-
Use server-timing for trace context response w3c/trace-context#560, by @dyladan.
-
-
2 pull requests merged.
-
Backport #558 uniform distribution w3c/trace-context#559.
-
fix: ensure random part of trace id is uniformly distributed w3c/trace-context#558.
-
-
2 pull requests received 3 new comments.
-
Use server-timing for trace context response w3c/trace-context#560 (2 comments by @dmathieu, @SergeyKanzhelev)
-
w3c/baggage
-
3 issues opened.
-
We need to document the reasoning for the supported character range w3c/baggage#128, by @kalyanaj.
-
-
4 issues closed.
-
Clarify whether length is in bytes or characters w3c/baggage#55.
-
Keys don't permit non-ASCII? w3c/baggage#99.
-
-
4 issues received 13 new comments.
-
Clarify whether length is in bytes or characters w3c/baggage#55 (3 comments by @aphillips, @dyladan, @SergeyKanzhelev)
-
When multiple baggage headers are used, clarify that minimum limits apply to the cumulative total w3c/baggage#126 (3 comments by @jcopi, @kalyanaj)
-
Baggage: Mention about minimum limits approach first before describing the conditions w3c/baggage#127 (1 comment by @kalyanaj)
-
2 pull requests opened.
-
Use the term code point where character may be ambiguous w3c/baggage#130, by @dyladan.
-
Update the Status of the document w3c/baggage#129, by @plehegar.
-
-
1 pull request merged.
-
Update the Status of the document w3c/baggage#129.
-
-
1 pull request closed.
-
Allow unicode in baggage keys by referencing XML w3c/baggage#120.
-
-
2 pull requests received 4 new comments.
-
Use the term code point where character may be ambiguous w3c/baggage#130 (3 comments by @kalyanaj, @SergeyKanzhelev)
-
w3c/tracestate-ids-registry
-
2 issues closed.
-
Register B3 w3c/tracestate-ids-registry#2.
-
Rename repository to tracestate-ids-registry w3c/tracestate-ids-registry#11.
-
-
2 issues received 2 new comments.
-
Rename repository to tracestate-ids-registry w3c/tracestate-ids-registry#11 (1 comment by @basti1302)
-
1 pull request opened.
-
Add SmartBear to registry w3c/tracestate-ids-registry#19, by @gareththackeray.
-
-
3 pull requests merged.
-
Editorial: Changed link to reflect repository renaming w3c/tracestate-ids-registry#13.
-
Add sn vendor code for ServiceNow trace state w3c/tracestate-ids-registry#18.
-
Add SmartBear to registry w3c/tracestate-ids-registry#19.
-
TR publications
-
1 document published.
-
Propagation format for distributed context: Baggage published as a Working Draft. History of Propagation format for distributed context: Baggage
-
Past meetings
Participants
-
1 participant joined.
-
Bastian Krol (W3C Invited Experts) joined.
-
-
1 participant left.
-
Bastian Krol (W3C Invited Experts) left.
-
GitHub
w3c/trace-context
-
1 issue opened.
-
Revisit header name -- Server-Timing vs. traceresponse w3c/trace-context#556, by @jpkrohling.
-
-
5 issues received 9 new comments.
-
Revisit header name -- Server-Timing vs. traceresponse w3c/trace-context#556 (5 comments by @basti1302, @dyladan, @kalyanaj)
-
Random part of trace ID should be uniformly distributed w3c/trace-context#544 (1 comment by @dyladan)
-
Proposal: Add a "propagation-only-parent" flag to be set to true if parents is a no-tracing service w3c/trace-context#550 (1 comment by @bogdandrutu)
-
w3c/trace-context#69 (1 comment by @jpkrohling)
-
Should tracing headers be included in 304 Not Modified responses? w3c/trace-context#554 (1 comment by @mitar)
-
-
3 pull requests opened.
-
Backport #558 uniform distribution w3c/trace-context#559, by @dyladan.
-
fix: ensure random part of trace id is uniformly distributed w3c/trace-context#558, by @dyladan.
-
update affiliation w3c/trace-context#557, by @basti1302.
-
-
1 pull request merged.
-
update affiliation w3c/trace-context#557.
-
-
2 pull requests received 11 new comments.
-
fix: ensure random part of trace id is uniformly distributed w3c/trace-context#558 (10 comments by @dyladan, @oertl, @PeterF778)
-
w3c/baggage
-
1 issue closed.
-
Precent character in value must be precent-encoded w3c/baggage#124.
-
-
2 issues received 3 new comments.
-
1 pull request merged.
-
Percent character in value MUST be percent-encoded w3c/baggage#125.
-
-
1 pull request received 1 new comment.