Distributed Tracing Working Group - Activity in 2021
No matches.
TR publications
-
1 document published.
Past meetings
GitHub
w3c/trace-context
-
1 issue closed.
-
Release trace context level-1 w3c/trace-context#469.
-
-
2 issues received 2 new comments.
-
1 pull request merged.
-
add required "on" trigger to Github action "self-test" w3c/trace-context#478.
-
-
3 pull requests received 12 new comments.
-
Specify uniqueness of tracestate keys as the sender's responsibility w3c/trace-context#477 (8 comments by @basti1302, @kalyanaj, @yurishkuro)
-
Specify expected behaviour when no traceparent is received w3c/trace-context#475 (3 comments by @basti1302, @kalyanaj)
-
w3c/baggage
-
4 issues opened.
-
Different behaviour in private browsing/incognito mode? w3c/baggage#84, by @hadleybeeman.
-
Reference the relevant RFC for URL encoding baggage values w3c/baggage#81, by @kalyanaj.
-
-
1 issue received 1 new comment.
-
Name 'baggage' is a metaphor and could be hard for non-native English speakers w3c/baggage#83 (1 comment by @kalyanaj)
-
-
2 pull requests opened.
-
Use RFC 7230 for token definition w3c/baggage#79, by @dyladan.
-
2 pull requests merged.
-
Apply url encoding to single header example, matching multiple w3c/baggage#78.
-
Use RFC 7230 for token definition w3c/baggage#79.
-
-
1 pull request reopened.
-
Apply url encoding to single header example, matching multiple w3c/baggage#78, by @plehegar.
-
-
2 pull requests received 3 new comments.
-
Apply url encoding to single header example, matching multiple w3c/baggage#78 (2 comments by @plehegar, @w3cbot)
-
TR publications
-
1 document published.
-
Trace Context published as a Recommendation. History of Trace Context
-
Past meetings
GitHub
w3c/trace-context
-
6 issues closed.
-
Can the intelligence-free nature of ids be confirmed or audited by external parties? w3c/trace-context#394.
-
Should response header fields be optional? w3c/trace-context#398.
-
term `negative sampling decision` may not be very clear to a reader w3c/trace-context#444.
-
Confusion between vendor and tenant in tracestate keys w3c/trace-context#459.
-
Level-1 Erratum Invalid ABNF w3c/trace-context#461.
-
level-1 branch contains changes not in level-1 w3c/trace-context#460.
-
-
10 issues received 32 new comments.
-
Clarify tracestate keys MUST be unique w3c/trace-context#446 (9 comments by @basti1302, @dyladan, @yurishkuro)
-
Release trace context level-1 w3c/trace-context#469 (8 comments by @basti1302, @dyladan, @plehegar, @swickr)
-
Vendor information in the response from traced service w3c/trace-context#466 (5 comments by @basti1302, @kalyanaj, @wjch-krl, @yurishkuro)
-
Can the intelligence-free nature of ids be confirmed or audited by external parties? w3c/trace-context#394 (2 comments by @kalyanaj, @npdoty)
-
Expected behavior with regard to starting a trace should be spelled out explicitly w3c/trace-context#442 (2 comments by @basti1302, @kalyanaj)
-
Be consistent with normative / non-normative sections w3c/trace-context#396 (1 comment by @kalyanaj)
-
-
7 pull requests opened.
-
An alternative proposal on implementing randomness by updating level … w3c/trace-context#480, by @SergeyKanzhelev.
-
must->should for keys mutation fix up w3c/trace-context#479, by @SergeyKanzhelev.
-
add required "on" trigger to Github action "self-test" w3c/trace-context#478, by @basti1302.
-
Specify uniqueness of tracestate keys as the sender's responsibility w3c/trace-context#477, by @basti1302.
-
Rephrase deferred sampling example w3c/trace-context#476, by @basti1302.
-
Specify expected behaviour when no traceparent is received w3c/trace-context#475, by @basti1302.
-
Add the random trace id flag w3c/trace-context#474, by @dyladan.
-
-
2 pull requests merged.
-
must->should for keys mutation fix up w3c/trace-context#479.
-
Rephrase deferred sampling example w3c/trace-context#476.
-
-
7 pull requests received 42 new comments.
-
Add the random trace id flag w3c/trace-context#474 (18 comments by @basti1302, @bogdandrutu, @dyladan, @yurishkuro)
-
Specify uniqueness of tracestate keys as the sender's responsibility w3c/trace-context#477 (12 comments by @basti1302, @dyladan, @SergeyKanzhelev, @yurishkuro)
-
An alternative proposal on implementing randomness by updating level … w3c/trace-context#480 (5 comments by @dyladan, @SergeyKanzhelev, @yurishkuro)
-
add required "on" trigger to Github action "self-test" w3c/trace-context#478 (3 comments by @basti1302, @SergeyKanzhelev)
-
Specify expected behaviour when no traceparent is received w3c/trace-context#475 (1 comment by @basti1302)
-
w3c/tracestate-ids-registry
-
3 pull requests merged.
-
Add SolarWinds identifier sw w3c/tracestate-ids-registry#14.
-
Add ls=Lightstep w3c/tracestate-ids-registry#16.
-
Add ot=OpenTelemtry w3c/tracestate-ids-registry#15.
-
-
2 pull requests received 3 new comments.
-
Add SolarWinds identifier sw w3c/tracestate-ids-registry#14 (2 comments by @cheempz, @SergeyKanzhelev)
-
Past meetings
GitHub
w3c/trace-context
-
1 issue opened.
-
Behavior when passing tracestate of '' w3c/trace-context#470, by @bizob2828.
-
-
1 issue closed.
-
Behavior when passing tracestate of '' w3c/trace-context#470.
-
-
2 issues received 5 new comments.
-
3 pull requests opened.
-
Update branch references from master to main w3c/trace-context#473, by @philsttr.
-
ReSpec fix w3c/trace-context#472, by @xfq.
-
Remove assertion that asserts a tracestate should not be created when empty w3c/trace-context#471, by @bizob2828.
-
-
3 pull requests merged.
-
Remove assertion that asserts a tracestate should not be created when empty w3c/trace-context#471.
-
Update branch references from master to main w3c/trace-context#473.
-
ReSpec fix w3c/trace-context#472.
-
-
2 pull requests received 9 new comments.
-
Remove assertion that asserts a tracestate should not be created when empty w3c/trace-context#471 (8 comments by @bizob2828, @danielkhan, @dyladan, @w3cbot)
-
w3c/trace-context-protocols-registry
-
1 pull request opened.
-
Update branch references from master to main w3c/trace-context-protocols-registry#12, by @philsttr.
-
w3c/baggage
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Apply url encoding to single header example, matching multiple w3c/baggage#78, by @anuraaga.
-
-
1 pull request received 8 new comments.
-
Apply url encoding to single header example, matching multiple w3c/baggage#78 (8 comments by @anuraaga, @yurishkuro)
-
w3c/tracestate-ids-registry
-
3 pull requests opened.
-
Add ls=Lightstep w3c/tracestate-ids-registry#16, by @jmacd.
-
Add ot=OpenTelemtry w3c/tracestate-ids-registry#15, by @jmacd.
-
Add SolarWinds identifier sw w3c/tracestate-ids-registry#14, by @cheempz.
-
-
2 pull requests received 3 new comments.
-
Add SolarWinds identifier sw w3c/tracestate-ids-registry#14 (2 comments by @cheempz, @SergeyKanzhelev)
-
TR publications
-
1 document published.
Past meetings
Participants
-
1 participant joined.
-
Bastian Krol (W3C Invited Experts) joined.
-
GitHub
w3c/trace-context
-
3 issues opened.
-
Release trace context level-1 w3c/trace-context#469, by @dyladan.
-
Randomness flag bit w3c/trace-context#467, by @bogdandrutu.
-
Vendor information in the response from traced service w3c/trace-context#466, by @wjch-krl.
-
-
2 issues received 8 new comments.
-
1 pull request opened.
-
Add sampling constant w3c/trace-context#468, by @dyladan.
-
-
2 pull requests merged.
-
fix(#459): remove confusing vendor/tenant wording w3c/trace-context#465.
-
Move Daniel Khan to former editors w3c/trace-context#462.
-
-
2 pull requests received 11 new comments.
-
fix(#459): remove confusing vendor/tenant wording w3c/trace-context#465 (3 comments by @dyladan, @kalyanaj)
w3c/baggage
-
1 issue opened.
-
Baggage value clarification for parsing w3c/baggage#77, by @srikanthccv.
-
-
2 issues closed.
-
Publish FPWD w3c/baggage#75.
-
Baggage value clarification for parsing w3c/baggage#77.
-
-
2 issues received 2 new comments.
-
1 pull request merged.
-
Move Daniel Khan to former editors w3c/baggage#76.
-
TR publications
-
1 document published.
Past meetings
Participants
-
1 participant left.
-
Sandeep Nayak (Adobe) left.
-
GitHub
w3c/trace-context
-
3 issues opened.
-
Consider trace context support for probability sampling w3c/trace-context#463, by @jmacd.
-
Level-1 Erratum Invalid ABNF w3c/trace-context#461, by @dyladan.
-
level-1 branch contains changes not in level-1 w3c/trace-context#460, by @dyladan.
-
-
1 issue closed.
-
Clarify how tracestate can or cannot be used by application developers w3c/trace-context#439.
-
-
5 issues received 9 new comments.
-
Consider trace context support for probability sampling w3c/trace-context#463 (2 comments by @dyladan, @jmacd)
-
Confusion between vendor and tenant in tracestate keys w3c/trace-context#459 (2 comments by @dyladan, @SergeyKanzhelev)
-
3 pull requests opened.
-
fix(#459): remove confusing vendor/tenant wording w3c/trace-context#465, by @dyladan.
-
fix: Backport #432 invalid ABNF w3c/trace-context#464, by @dyladan.
-
Move Daniel Khan to former editors w3c/trace-context#462, by @dyladan.
-
-
2 pull requests merged.
-
Updated tracestate to specify that it should not be used for application level properties w3c/trace-context#458.
-
fix: Backport #432 invalid ABNF w3c/trace-context#464.
-
-
3 pull requests received 15 new comments.
-
fix(#459): remove confusing vendor/tenant wording w3c/trace-context#465 (8 comments by @dyladan, @kalyanaj, @SergeyKanzhelev)
-
Updated tracestate to specify that it should not be used for application level properties w3c/trace-context#458 (5 comments by @dyladan, @plehegar, @SergeyKanzhelev)
-
w3c/baggage
-
1 issue opened.
-
Publish FPWD w3c/baggage#75, by @SergeyKanzhelev.
-
-
2 issues closed.
-
Switch this specification to auto-publishing w3c/baggage#63.
-
Do not refer to "traces" in the baggage spec w3c/baggage#28.
-
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Move Daniel Khan to former editors w3c/baggage#76, by @dyladan.
-
-
2 pull requests merged.
-
Add auto-publish.yml w3c/baggage#73.
-
Replace references to "traces" with "distributed request". w3c/baggage#71.
-
-
1 pull request closed.
-
Move non-format information to overview and expand w3c/baggage#72.
-
-
1 pull request received 1 new comment.
Past meetings
Participants
-
1 chair appointed.
-
J. Kalyana Sundaram became a chair.
-
-
1 chair stepped down.
-
Daniel Khan stepped down as a chair.
-
-
1 participant left.
-
Daniel Khan (Dynatrace LLC) left.
-
GitHub
w3c/trace-context
-
1 issue opened.
-
Confusion between vendor and tenant in tracestate keys w3c/trace-context#459, by @taylor-hunt-kr.
-
-
2 issues received 3 new comments.
-
Clarify handling of duplicate keys in tracestate w3c/trace-context#369 (2 comments by @dyladan, @reyang)
-
w3c/trace-context#119 (1 comment by @alexweej)
-
-
2 pull requests opened.
-
Updated tracestate to specify that it should not be used for application level properties w3c/trace-context#458, by @kalyanaj.
-
.travis.yml is no longer needed w3c/trace-context#457, by @plehegar.
-
-
2 pull requests merged.
-
.travis.yml is no longer needed w3c/trace-context#457.
-
Update editors to reflect current contributors w3c/trace-context#456.
-
-
1 pull request received 5 new comments.
-
Updated tracestate to specify that it should not be used for application level properties w3c/trace-context#458 (5 comments by @kalyanaj, @SergeyKanzhelev, @yurishkuro)
-
w3c/baggage
-
4 issues opened.
-
Create a test as a reference implementation w3c/baggage#74, by @kalyanaj.
-
Add information about reference implementations to README. w3c/baggage#68, by @kalyanaj.
-
Consider lowering baggage limits w3c/baggage#65, by @dyladan.
-
Switch this specification to auto-publishing w3c/baggage#63, by @plehegar.
-
-
4 issues closed.
-
revert arbitrary "cookie" rationale w3c/baggage#22.
-
Use cases for Baggage w3c/baggage#10.
-
Add information about reference implementations to README. w3c/baggage#68.
-
Update Editors w3c/baggage#40.
-
-
2 issues received 4 new comments.
-
8 pull requests opened.
-
Add auto-publish.yml w3c/baggage#73, by @plehegar.
-
Move non-format information to overview and expand w3c/baggage#72, by @dyladan.
-
Replace references to "traces" with "distributed request". w3c/baggage#71, by @kalyanaj.
-
Add few use cases for baggage. w3c/baggage#70, by @kalyanaj.
-
Add section about baggage mutations w3c/baggage#67, by @dyladan.
-
Add a security section w3c/baggage#66, by @dyladan.
-
Remove arbitrary cookie rationale w3c/baggage#64, by @dyladan.
-
-
6 pull requests merged.
-
Remove arbitrary cookie rationale w3c/baggage#64.
-
Add section about baggage mutations w3c/baggage#67.
-
Add a security section w3c/baggage#66.
-
Add few use cases for baggage. w3c/baggage#70.
-
Update editors to reflect current contributors w3c/baggage#62.
-
-
2 pull requests closed.
-
Add section about Mutating baggage w3c/baggage#50.
-
Add security section w3c/baggage#47.
-
-
8 pull requests received 22 new comments.
-
Replace references to "traces" with "distributed request". w3c/baggage#71 (7 comments by @dyladan, @kalyanaj, @yurishkuro)
-
Added information about reference implementations of the baggage specification w3c/baggage#69 (2 comments by @dyladan, @kalyanaj)
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
William Holroyd (Lenovo) joined.
-
-
1 organization joined.
-
Lenovo joined.
-
GitHub
w3c/baggage
-
2 pull requests opened.
-
Update editors to reflect current contributors w3c/baggage#62, by @danielkhan.
-
a few small fixes w3c/baggage#61, by @SergeyKanzhelev.
-
-
1 pull request merged.
-
a few small fixes w3c/baggage#61.
-
-
2 pull requests received 7 new comments.
w3c/trace-context
-
1 issue closed.
-
Use of W3C Trace-Context with multiple agents in a single process, inject issue w3c/trace-context#451.
-
-
1 issue received 2 new comments.
-
Use of W3C Trace-Context with multiple agents in a single process, inject issue w3c/trace-context#451 (2 comments by @kamtschatka, @SergeyKanzhelev)
-
-
2 pull requests opened.
-
Update editors to reflect current contributors w3c/trace-context#456, by @danielkhan.
-
Move to GitHub actions w3c/trace-context#455, by @plehegar.
-
-
1 pull request merged.
-
Move to GitHub actions w3c/trace-context#455.
-
-
2 pull requests received 5 new comments.
-
Move to GitHub actions w3c/trace-context#455 (4 comments by @plehegar, @SergeyKanzhelev, @yurishkuro)
-
Past meetings
-
1 meeting.
Participants
-
1 Team contact appointed.
-
Philippe Le Hegaret became a Team contact.
-
-
1 Team contact stepped down.
-
Carine Bournez stepped down as a Team contact.
-
-
1 participant joined.
-
David Caro (Wikimedia Foundation) joined.
-
-
1 participant left.
-
Carine Bournez (W3C) left.
-
-
1 organization joined.
-
Wikimedia Foundation joined.
-
GitHub
w3c/trace-context
-
1 issue closed.
-
Rename master branch to main w3c/trace-context#454.
-
-
1 issue received 1 new comment.
w3c/baggage
-
1 issue opened.
-
Rename master branch to main w3c/baggage#60, by @plehegar.
-
-
1 issue closed.
-
Rename master branch to main w3c/baggage#60.
-
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Fix the path to privacy.md w3c/baggage#59, by @SergeyKanzhelev.
-
-
1 pull request merged.
-
Fix the path to privacy.md w3c/baggage#59.
-
-
1 pull request received 3 new comments.
GitHub
w3c/trace-context
-
3 issues opened.
-
Rename master branch to main w3c/trace-context#454, by @dyladan.
-
Microsoft nominates new member as Chair w3c/trace-context#453, by @Kanwaldeep.
-
Add "request" to glossary w3c/trace-context#452, by @SergeyKanzhelev.
-
-
1 issue closed.
-
Microsoft nominates new member as Chair w3c/trace-context#453.
-
-
2 issues received 4 new comments.
-
Microsoft nominates new member as Chair w3c/trace-context#453 (3 comments by @caribouW3, @danielkhan, @yurishkuro)
-
-
1 pull request closed.
-
Create first draft of the use cases document w3c/trace-context#425.
-
w3c/baggage
-
5 issues opened.
-
Requirement to strip OWS out of scope w3c/baggage#58, by @dyladan.
-
Current ABNF only allows for single-character baggage value w3c/baggage#56, by @dyladan.
-
Clarify whether length is in bytes or characters w3c/baggage#55, by @SergeyKanzhelev.
-
Remove optional whitespace w3c/baggage#53, by @dyladan.
-
Do name-value pair limits include the equals sign? w3c/baggage#51, by @anuraaga.
-
-
4 issues closed.
-
Current ABNF only allows for single-character baggage value w3c/baggage#56.
-
Do name-value pair limits include the equals sign? w3c/baggage#51.
-
Clarify if values are allowed to contain `=` w3c/baggage#34.
-
-
4 issues received 11 new comments.
-
8 pull requests opened.
-
Extend ABNF to allow multi-octet values w3c/baggage#57, by @dyladan.
-
Remove optional whitespace w3c/baggage#54, by @dyladan.
-
Clarify ABNF limits w3c/baggage#52, by @dyladan.
-
Add section about Mutating baggage w3c/baggage#50, by @danielkhan.
-
Adds a Privacy section w3c/baggage#49, by @danielkhan.
-
fix #25: remove inconsistency w3c/baggage#48, by @SergeyKanzhelev.
-
Add security section w3c/baggage#47, by @danielkhan.
-
fix #34: note, that equal sign can be used in the value w3c/baggage#46, by @SergeyKanzhelev.
-
-
5 pull requests merged.
-
Adds a Privacy section w3c/baggage#49.
-
Extend ABNF to allow multi-octet values w3c/baggage#57.
-
Clarify ABNF limits w3c/baggage#52.
-
fix #34: note, that equal sign can be used in the value w3c/baggage#46.
-
fix #25: remove inconsistency w3c/baggage#48.
-
-
1 pull request closed.
-
Remove optional whitespace w3c/baggage#54.
-
-
6 pull requests received 46 new comments.
-
Add section about Mutating baggage w3c/baggage#50 (15 comments by @danielkhan, @dyladan, @SergeyKanzhelev, @yurishkuro)
-
Adds a Privacy section w3c/baggage#49 (12 comments by @danielkhan, @kalyanaj, @SergeyKanzhelev, @yurishkuro)
-
Participants
-
2 participants joined.
-
J. Kalyana Sundaram (Microsoft Corporation) joined.
-
Yuri Shkuro (Meta) joined.
-
-
1 organization joined.
-
Meta joined.
-
GitHub
w3c/tracestate-ids-registry
-
1 issue closed.
-
Use issues and issue templates instead of a PR to request a new ID w3c/tracestate-ids-registry#1.
-
-
1 issue received 2 new comments.
-
Rename repository to tracestate-ids-registry w3c/tracestate-ids-registry#11 (2 comments by @caribouW3, @danielkhan)
-
-
1 pull request opened.
-
Editorial: Changed link to reflect repository renaming w3c/tracestate-ids-registry#13, by @danielkhan.
-
-
1 pull request merged.
-
trace-state to tracestate w3c/tracestate-ids-registry#10.
-
w3c/trace-context
-
4 issues closed.
-
Clarify use of trace-id in response header w3c/trace-context#407.
-
How to preserve trace context on http redirect ? w3c/trace-context#438.
-
Should a tracestate key always be allowed to start with a lowercase letter or digit? w3c/trace-context#441.
-
Move response header Returning the traceresponse Field to non-normative processing section. w3c/trace-context#445.
-
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Move traceresponse processing to processing model w3c/trace-context#450.
-
Participants
-
1 chair appointed.
-
Sergey Kanzhelev became a chair.
-
-
7 participants left.
-
Aaron Watts (New Relic, Inc.) left.
-
Justin Foote (New Relic, Inc.) left.
-
Tyler Yahn (New Relic, Inc.) left.
-
Chris Hansen (New Relic, Inc.) left.
-
Martin Kuba (New Relic, Inc.) left.
-
Erika Arnold (New Relic, Inc.) left.
-
Yuri Shkuro (Meta) left.
-
-
1 organization left.
-
New Relic, Inc. left.
-
GitHub
w3c/trace-context
-
1 issue opened.
-
Use of W3C Trace-Context with multiple agents in a single process, inject issue w3c/trace-context#451, by @pavolloffay.
-
-
2 issues received 7 new comments.
-
How to preserve trace context on http redirect ? w3c/trace-context#438 (6 comments by @dmitriyse, @dyladan, @yurishkuro)
-
Use of W3C Trace-Context with multiple agents in a single process, inject issue w3c/trace-context#451 (1 comment by @danielkhan)
-
-
1 pull request received 3 new comments.
-
Move traceresponse processing to processing model w3c/trace-context#450 (3 comments by @cwensel, @dyladan, @Kanwaldeep)
-
w3c/tracestate-ids-registry
-
2 pull requests merged.
-
Add dt identifier w3c/tracestate-ids-registry#12.
-
Add New Relic tracestate identifier w3c/tracestate-ids-registry#7.
-
Participants
-
1 chair stepped down.
-
Morgan McLean stepped down as a chair.
-
-
1 participant left.
-
Morgan McLean (Google LLC) left.
-
GitHub
w3c/trace-context
-
2 issues opened.
-
Define entry/value length/size consistently w3c/trace-context#449, by @dyladan.
-
Consider renaming parent-id / child-id to span-id w3c/trace-context#447, by @mwear.
-
-
4 issues closed.
-
How should tracestate list members be truncated when they exceed 32? w3c/trace-context#440.
-
Encourage traceresponse to be provided even when traceparent is used w3c/trace-context#437.
-
Remove proposed-parent-id from response header w3c/trace-context#406.
-
Consider renaming parent-id / child-id to span-id w3c/trace-context#447.
-
-
4 issues received 31 new comments.
-
Clarify tracestate keys MUST be unique w3c/trace-context#446 (20 comments by @anuraaga, @danielkhan, @dyladan, @jkwatson, @SergeyKanzhelev, @yurishkuro)
-
Consider renaming parent-id / child-id to span-id w3c/trace-context#447 (8 comments by @dyladan, @mwear, @SergeyKanzhelev, @yurishkuro)
-
Should a tracestate key always be allowed to start with a lowercase letter or digit? w3c/trace-context#441 (2 comments by @dyladan)
-
How should tracestate list members be truncated when they exceed 32? w3c/trace-context#440 (1 comment by @dyladan)
-
-
2 pull requests opened.
-
Move traceresponse processing to processing model w3c/trace-context#450, by @dyladan.
-
When the 32-entry limit is met, the right-most entry is removed w3c/trace-context#448, by @dyladan.
-
-
2 pull requests merged.
-
When the 32-entry limit is met, the right-most entry is removed w3c/trace-context#448.
-
Replace proposed-parent-id with child-id. All fields required. w3c/trace-context#443.
-
-
3 pull requests received 13 new comments.
-
Replace proposed-parent-id with child-id. All fields required. w3c/trace-context#443 (9 comments by @dyladan, @yurishkuro)
-
When the 32-entry limit is met, the right-most entry is removed w3c/trace-context#448 (3 comments by @dyladan, @SergeyKanzhelev, @yurishkuro)
-
w3c/tracestate-ids-registry
-
1 pull request opened.
-
Add dt identifier w3c/tracestate-ids-registry#12, by @dyladan.
-