Distributed Tracing Working Group - Activity in 2020
No matches.
Participants
-
1 participant joined.
-
Andrew Arnott (Microsoft Corporation) joined.
-
GitHub
w3c/tracestate-ids-registry
-
1 issue received 3 new comments.
w3c/trace-context
-
7 issues opened.
-
Clarify tracestate keys MUST be unique w3c/trace-context#446, by @codefromthecrypt.
-
Move response header Returning the traceresponse Field to non-normative processing section. w3c/trace-context#445, by @dyladan.
-
term `negative sampling decision` may not be very clear to a reader w3c/trace-context#444, by @dyladan.
-
Expected behavior with regard to starting a trace should be spelled out explicitly w3c/trace-context#442, by @basti1302.
-
Should a tracestate key always be allowed to start with a lowercase letter or digit? w3c/trace-context#441, by @MrAlias.
-
How should tracestate list members be truncated when they exceed 32? w3c/trace-context#440, by @MrAlias.
-
Clarify how tracestate can or cannot be used by application developers w3c/trace-context#439, by @gfraiteur.
-
-
4 issues closed.
-
Bogus trace and parent IDs when not sampling w3c/trace-context#390.
-
Backport #423 to `level-1` w3c/trace-context#424.
-
Erratum level-1: Contradiction in TraceState w3c/trace-context#428.
-
What's the recommended guideline for generating parent-id? w3c/trace-context#412.
-
-
1 issue reopened.
-
ABNF improvement w3c/trace-context#364, by @danielkhan.
-
-
7 issues received 13 new comments.
-
Should response header fields be optional? w3c/trace-context#398 (3 comments by @dyladan, @yurishkuro)
-
Encourage traceresponse to be provided even when traceparent is used w3c/trace-context#437 (2 comments by @briancr-ms, @dyladan)
-
Clarify how tracestate can or cannot be used by application developers w3c/trace-context#439 (2 comments by @gfraiteur, @yurishkuro)
-
-
1 pull request opened.
-
Replace proposed-parent-id with child-id. All fields required. w3c/trace-context#443, by @dyladan.
-
-
2 pull requests merged.
-
Clarify behaviour when starting a trace and not recording w3c/trace-context#433.
-
Add wording suggesting random generation of span ids w3c/trace-context#426.
-
-
3 pull requests received 13 new comments.
-
Replace proposed-parent-id with child-id. All fields required. w3c/trace-context#443 (8 comments by @danielkhan, @dyladan, @SergeyKanzhelev)
-
Clarify behaviour when starting a trace and not recording w3c/trace-context#433 (4 comments by @basti1302, @danielkhan, @w3cbot, @yurishkuro)
-
w3c/trace-context-protocols-registry
-
1 issue received 2 new comments.
GitHub
w3c/trace-context-protocols-registry
-
1 issue closed.
-
Register cloud events tracecontext extension w3c/trace-context-protocols-registry#7.
-
-
1 issue received 7 new comments.
-
w3c/trace-context-protocols-registry#4 (7 comments by @AArnott, @caribouW3, @nrktkt, @SergeyKanzhelev)
-
-
1 pull request merged.
-
added cloud events w3c/trace-context-protocols-registry#11.
-
-
1 pull request received 1 new comment.
w3c/trace-context
-
1 issue opened.
-
How to preserve trace context on http redirect ? w3c/trace-context#438, by @dmitriyse.
-
-
1 issue closed.
-
Clarify "opaque" w3c/trace-context#348.
-
-
1 issue received 4 new comments.
-
How to preserve trace context on http redirect ? w3c/trace-context#438 (4 comments by @dmitriyse, @SergeyKanzhelev)
-
-
5 pull requests merged.
-
fixing ABNF, related to #364 w3c/trace-context#432.
-
Backport to level-1: Remove contradiction in TraceState mutations w3c/trace-context#430.
-
Opaque glossary w3c/trace-context#434.
-
small cleanup w3c/trace-context#436.
-
change SergeyKanzhelev's affiliation w3c/trace-context#431.
-
-
4 pull requests received 14 new comments.
-
Clarify behaviour when starting a trace and not recording w3c/trace-context#433 (5 comments by @anuraaga, @basti1302, @yurishkuro)
-
fixing ABNF, related to #364 w3c/trace-context#432 (3 comments by @arminru, @danielkhan, @SergeyKanzhelev)
-
Add wording suggesting random generation of span ids w3c/trace-context#426 (1 comment by @danielkhan)
w3c/distributed-tracing-wg
-
1 issue closed.
-
Goal of the working group needs to be updated w3c/distributed-tracing-wg#45.
-
-
2 pull requests merged.
-
Rename Correlation-Context to Baggage w3c/distributed-tracing-wg#47.
-
Cleanups w3c/distributed-tracing-wg#48.
-
TR publications
-
1 document published.
-
Propagation format for distributed trace context: Baggage published as a First Public Working Draft. History of Propagation format for distributed trace context: Baggage
-
Participants
-
2 participants joined.
-
Aaron Watts (New Relic, Inc.) joined.
-
Caio Gondim (The New York Times) joined.
-
-
1 participant left.
-
Victor Soares (New Relic, Inc.) left.
-
-
2 organizations joined.
-
ZIIOT joined.
-
The New York Times joined.
-
GitHub
w3c/tracestate-ids-registry
-
1 issue opened.
-
Rename repository to tracestate-ids-registry w3c/tracestate-ids-registry#11, by @SergeyKanzhelev.
-
-
1 issue closed.
-
Update format to remove contact w3c/tracestate-ids-registry#8.
-
-
2 pull requests opened.
-
trace-state to tracestate w3c/tracestate-ids-registry#10, by @SergeyKanzhelev.
-
Add es identifier for Elastic w3c/tracestate-ids-registry#9, by @hmdhk.
-
-
1 pull request merged.
-
Add es identifier for Elastic w3c/tracestate-ids-registry#9.
-
-
1 pull request received 1 new comment.
w3c/trace-context-protocols-registry
-
2 pull requests opened.
-
added cloud events w3c/trace-context-protocols-registry#11, by @SergeyKanzhelev.
-
small cleanup w3c/trace-context-protocols-registry#10, by @SergeyKanzhelev.
-
-
1 pull request merged.
-
small cleanup w3c/trace-context-protocols-registry#10.
-
w3c/trace-context
-
2 issues opened.
-
Encourage traceresponse to be provided even when traceparent is used w3c/trace-context#437, by @briancr-ms.
-
Erratum level-1: Contradiction in TraceState w3c/trace-context#428, by @dyladan.
-
-
2 issues closed.
-
Test suite server crashes with newer multidict version w3c/trace-context#366.
-
Contradiction in TraceState requirements w3c/trace-context#422.
-
-
7 issues received 9 new comments.
-
Encourage traceresponse to be provided even when traceparent is used w3c/trace-context#437 (3 comments by @briancr-ms, @dyladan, @SergeyKanzhelev)
-
Remove proposed-parent-id from response header w3c/trace-context#406 (1 comment by @codefromthecrypt)
-
-
10 pull requests opened.
-
small cleanup w3c/trace-context#436, by @SergeyKanzhelev.
-
Replace all-upper case CAN with MAY w3c/trace-context#435, by @basti1302.
-
Opaque glossary w3c/trace-context#434, by @SergeyKanzhelev.
-
Clarify behaviour when starting a trace and not recording w3c/trace-context#433, by @basti1302.
-
fixing ABNF, related to #364 w3c/trace-context#432, by @SergeyKanzhelev.
-
change SergeyKanzhelev's affiliation w3c/trace-context#431, by @SergeyKanzhelev.
-
Backport to level-1: Remove contradiction in TraceState mutations w3c/trace-context#430, by @dyladan.
-
Revert "Backport to level-1: Remove contradiction in TraceState mutations" w3c/trace-context#429, by @danielkhan.
-
Backport to level-1: Remove contradiction in TraceState mutations w3c/trace-context#427, by @dyladan.
-
Add wording suggesting random generation of span ids w3c/trace-context#426, by @dyladan.
-
-
4 pull requests merged.
-
Replace all-upper case CAN with MAY w3c/trace-context#435.
-
Revert "Backport to level-1: Remove contradiction in TraceState mutations" w3c/trace-context#429.
-
Backport to level-1: Remove contradiction in TraceState mutations w3c/trace-context#427.
-
Remove contradiction in TraceState mutations w3c/trace-context#423.
-
-
6 pull requests received 33 new comments.
-
Clarify behaviour when starting a trace and not recording w3c/trace-context#433 (14 comments by @basti1302, @SergeyKanzhelev, @yurishkuro)
-
Add wording suggesting random generation of span ids w3c/trace-context#426 (7 comments by @bogdandrutu, @dyladan, @SergeyKanzhelev, @yurishkuro)
-
Create first draft of the use cases document w3c/trace-context#425 (4 comments by @codefromthecrypt, @jcchavezs, @Kanwaldeep)
-
Backport to level-1: Remove contradiction in TraceState mutations w3c/trace-context#427 (4 comments by @caribouW3, @dyladan)
-
w3c/baggage
-
8 issues closed.
-
Review / update rationale w3c/baggage#26.
-
Security and encryption considerations w3c/baggage#12.
-
Support for a PII property of a Correlation Context value w3c/baggage#5.
-
One level down correlation context propagation (TTL=1) w3c/baggage#4.
-
OpenTelemetry and Correlation Context w3c/baggage#16.
-
remove Latest published version header w3c/baggage#21.
-
CfC: Move to First Public Working Draft w3c/baggage#36.
-
-
8 issues received 10 new comments.
-
CfC: Move to First Public Working Draft w3c/baggage#36 (3 comments by @caribouW3, @danielkhan, @dyladan)
-
Add rationale for why libraries MAY propagate or otherwise change to MUST w3c/baggage#25 (1 comment by @danielkhan)
-
-
2 pull requests opened.
-
small cleanup w3c/baggage#45, by @SergeyKanzhelev.
-
respec update w3c/baggage#44, by @caribouW3.
-
-
2 pull requests merged.
-
small cleanup w3c/baggage#45.
-
respec update w3c/baggage#44.
-
w3c/distributed-tracing-wg
-
3 issues closed.
-
charter: mark internal review snapshot as obsolete. w3c/distributed-tracing-wg#39.
-
Expected Completion dates w3c/distributed-tracing-wg#27.
-
Virtual workshop in Fall 2020 w3c/distributed-tracing-wg#44.
-
-
3 issues received 7 new comments.
-
Virtual workshop in Fall 2020 w3c/distributed-tracing-wg#44 (4 comments by @aw100, @danielkhan, @mwear)
-
charter: mark internal review snapshot as obsolete. w3c/distributed-tracing-wg#39 (2 comments by @caribouW3, @samuelweiler)
-
Explain multi-graph pattern of tracestate w3c/distributed-tracing-wg#28 (1 comment by @SergeyKanzhelev)
-
-
2 pull requests opened.
-
Cleanups w3c/distributed-tracing-wg#48, by @SergeyKanzhelev.
-
Rename Correlation-Context to Baggage w3c/distributed-tracing-wg#47, by @SergeyKanzhelev.
-
-
1 pull request merged.
-
Update references in readme w3c/distributed-tracing-wg#46.
-
Participants
-
1 participant joined.
-
Michael Lewis (LSEG) joined.
-
-
1 organization joined.
-
LSEG joined.
-
GitHub
w3c/baggage
-
4 issues opened.
-
Update Editors w3c/baggage#40, by @mtwo.
-
CfC: Move to First Public Working Draft w3c/baggage#36, by @danielkhan.
-
Add (normative) reference to RFC 2616 (HTTP/1.1) w3c/baggage#35, by @arminru.
-
Clarify if values are allowed to contain `=` w3c/baggage#34, by @arminru.
-
-
2 issues closed.
-
Add (normative) reference to RFC 2616 (HTTP/1.1) w3c/baggage#35.
-
Need to have concrete ABNF syntax w3c/baggage#8.
-
-
5 issues received 7 new comments.
-
limitations do not appear to have standard implementation for enforcement w3c/baggage#30 (1 comment by @danielkhan)
-
9 pull requests opened.
-
a few minor fixes into index.html w3c/baggage#43, by @SergeyKanzhelev.
-
Grammar nits w3c/baggage#42, by @mtwo.
-
Resolve personal branches w3c/baggage#41, by @mtwo.
-
Canonicalize header name as baggage w3c/baggage#39, by @mwear.
-
Fix gramar: an URL -> a URL w3c/baggage#38, by @yurishkuro.
-
Replace sample user name with customary "alice" w3c/baggage#37, by @yurishkuro.
-
Simplify grammar for list-member w3c/baggage#33, by @arminru.
-
Fix section hierarchy w3c/baggage#32, by @arminru.
-
Fix syntax definition syntax and references w3c/baggage#31, by @arminru.
-
-
8 pull requests merged.
-
Grammar nits w3c/baggage#42.
-
a few minor fixes into index.html w3c/baggage#43.
-
Resolve personal branches w3c/baggage#41.
-
Fix syntax definition syntax and references w3c/baggage#31.
-
Fix section hierarchy w3c/baggage#32.
-
Canonicalize header name as baggage w3c/baggage#39.
-
Replace sample user name with customary "alice" w3c/baggage#37.
-
Fix gramar: an URL -> a URL w3c/baggage#38.
-
-
1 pull request closed.
-
Simplify grammar for list-member w3c/baggage#33.
-
-
4 pull requests received 19 new comments.
-
Fix syntax definition syntax and references w3c/baggage#31 (9 comments by @arminru, @SergeyKanzhelev, @yurishkuro)
-
Simplify grammar for list-member w3c/baggage#33 (7 comments by @arminru, @ktoso, @mtwo, @SergeyKanzhelev, @yurishkuro)
-
w3c/trace-context
-
2 issues opened.
-
Backport #423 to `level-1` w3c/trace-context#424, by @dyladan.
-
Contradiction in TraceState requirements w3c/trace-context#422, by @dyladan.
-
-
2 issues received 5 new comments.
-
What's the recommended guideline for generating parent-id? w3c/trace-context#412 (1 comment by @dyladan)
-
3 pull requests opened.
-
Create first draft of the use cases document w3c/trace-context#425, by @danielkhan.
-
Remove contradiction in TraceState mutations w3c/trace-context#423, by @dyladan.
-
Improve wording on tracestate mutations w3c/trace-context#421, by @arminru.
-
-
2 pull requests merged.
-
Improve wording on tracestate mutations w3c/trace-context#421.
-
Add a document describing uses for optional fields w3c/trace-context#419.
-
-
2 pull requests received 10 new comments.
-
Improve wording on tracestate mutations w3c/trace-context#421 (7 comments by @anuraaga, @arminru, @dyladan)
-
Remove contradiction in TraceState mutations w3c/trace-context#423 (3 comments by @dyladan, @yurishkuro)
-
w3c/distributed-tracing-wg
-
2 issues opened.
-
Goal of the working group needs to be updated w3c/distributed-tracing-wg#45, by @arminru.
-
Virtual workshop in Fall 2020 w3c/distributed-tracing-wg#44, by @danielkhan.
-
-
1 issue received 7 new comments.
-
Virtual workshop in Fall 2020 w3c/distributed-tracing-wg#44 (7 comments by @caribouW3, @cwensel, @dyladan, @justinfoote, @Kanwaldeep, @mwear, @SergeyKanzhelev)
-
-
1 pull request opened.
-
Update references in readme w3c/distributed-tracing-wg#46, by @arminru.
-
Lifecycle
-
1 charter started.
-
Chartered until 30 September 2022.
-
Participants
-
1 Team contact appointed.
-
Carine Bournez became a Team contact.
-
-
1 Team contact stepped down.
-
Philippe Le Hegaret stepped down as a Team contact.
-
-
2 participants joined.
-
Carine Bournez (W3C) joined.
-
Aaron Young (IBM Corporation) joined.
-
-
1 organization joined.
-
IBM Corporation joined.
-
GitHub
w3c/trace-context
-
1 issue closed.
-
Fix key errors in test suite w3c/trace-context#416.
-
-
1 issue received 3 new comments.
-
Should response header fields be optional? w3c/trace-context#398 (3 comments by @dyladan, @yurishkuro)
-
-
3 pull requests opened.
-
Update implementations.md w3c/trace-context#420, by @productml-ai.
-
Add a document describing uses for optional fields w3c/trace-context#419, by @dyladan.
-
Add OpenTelemetry .NET to the implementation list w3c/trace-context#418, by @reyang.
-
-
3 pull requests merged.
-
Update implementations.md w3c/trace-context#420.
-
Add OpenTelemetry .NET to the implementation list w3c/trace-context#418.
-
Check if keys exist before trying to access them w3c/trace-context#417.
-
-
2 pull requests received 10 new comments.
w3c/baggage
-
1 issue opened.
-
limitations do not appear to have standard implementation for enforcement w3c/baggage#30, by @dmikey.
-
-
1 issue received 10 new comments.
-
limitations do not appear to have standard implementation for enforcement w3c/baggage#30 (10 comments by @dyladan, @michael-lewis-rft, @mtwo, @yurishkuro)
-
-
1 pull request opened.
-
Fix baggage link typo w3c/baggage#29, by @matthewgrossman.
-
-
1 pull request merged.
-
Fix baggage link typo w3c/baggage#29.
-
w3c/distributed-tracing-wg
-
1 issue opened.
-
charter: update history table w3c/distributed-tracing-wg#43, by @samuelweiler.
-
-
1 issue closed.
-
charter: clarify if/how/when this touches browsers and users w3c/distributed-tracing-wg#35.
-
-
2 issues received 3 new comments.
-
charter: clarify if/how/when this touches browsers and users w3c/distributed-tracing-wg#35 (2 comments by @plehegar, @samuelweiler)
-
charter: mark internal review snapshot as obsolete. w3c/distributed-tracing-wg#39 (1 comment by @samuelweiler)
-
Participants
-
1 participant joined.
-
Chris Wensel (Salesforce) joined.
-
-
1 organization joined.
-
Salesforce joined.
-
GitHub
w3c/trace-context
-
1 issue opened.
-
Fix key errors in test suite w3c/trace-context#416, by @srjames90.
-
-
4 issues closed.
-
[response header] Representing optional fields w3c/trace-context#400.
-
Add application insights to the list w3c/trace-context#339.
-
How multiple APMs in a process can "collaborate" on a given trace-context? w3c/trace-context#335.
-
Provide vendor/open source product name register for tracestate w3c/trace-context#58.
-
-
9 issues received 10 new comments.
-
Clarify handling of duplicate keys in tracestate w3c/trace-context#369 (2 comments by @danielkhan, @reyang)
-
Test suite server crashes with newer multidict version w3c/trace-context#366 (1 comment by @Oberon00)
-
w3c/trace-context#120 (1 comment by @danielkhan)
-
w3c/trace-context#58 (1 comment by @danielkhan)
-
-
4 pull requests opened.
-
Check if keys exist before trying to access them w3c/trace-context#417, by @srjames90.
-
Add .NET Core support for Instana w3c/trace-context#415, by @mmanciop.
-
Fix typo w3c/trace-context#414, by @flash-gordon.
-
Add PHP @ Instana support for W3C Trace Context w3c/trace-context#413, by @mmanciop.
-
-
3 pull requests merged.
-
Add .NET Core support for Instana w3c/trace-context#415.
-
Fix typo w3c/trace-context#414.
-
Add PHP @ Instana support for W3C Trace Context w3c/trace-context#413.
-
-
1 pull request received 1 new comment.
-
Check if keys exist before trying to access them w3c/trace-context#417 (1 comment by @SergeyKanzhelev)
-
w3c/tracestate-ids-registry
-
1 issue opened.
-
Update format to remove contact w3c/tracestate-ids-registry#8, by @dyladan.
-
-
1 issue closed.
-
New id: "in" (Instana) w3c/tracestate-ids-registry#4.
-
-
1 pull request opened.
-
Add New Relic tracestate identifier w3c/tracestate-ids-registry#7, by @justinfoote.
-
-
2 pull requests merged.
-
replace specification with company or implementor url w3c/tracestate-ids-registry#6.
-
Add the `in` prefix for Instana w3c/tracestate-ids-registry#5.
-
-
1 pull request received 1 new comment.
w3c/baggage
-
1 issue opened.
-
Do not refer to "traces" in the baggage spec w3c/baggage#28, by @danielkhan.
-
-
1 issue closed.
-
Rename the header to Baggage w3c/baggage#17.
-
-
1 issue received 7 new comments.
-
Rename the header to Baggage w3c/baggage#17 (7 comments by @codefromthecrypt, @danielkhan, @jcchavezs, @mwear, @r12a, @yurishkuro)
-
-
1 pull request opened.
-
Renaming to baggage w3c/baggage#27, by @danielkhan.
-
-
1 pull request merged.
-
Renaming to baggage w3c/baggage#27.
-
-
1 pull request received 11 new comments.
w3c/distributed-tracing-wg
-
2 issues opened.
-
Rename the correlation-context repo to baggage w3c/distributed-tracing-wg#42, by @danielkhan.
-
Change Bi-Weekly meeting time w3c/distributed-tracing-wg#41, by @danielkhan.
-
-
3 issues closed.
-
Rename the correlation-context repo to baggage w3c/distributed-tracing-wg#42.
-
Change Bi-Weekly meeting time w3c/distributed-tracing-wg#41.
-
charter: plan for getting user consent w3c/distributed-tracing-wg#36.
-
-
1 issue reopened.
-
Rename the correlation-context repo to baggage w3c/distributed-tracing-wg#42, by @danielkhan.
-
-
3 issues received 10 new comments.
-
Change Bi-Weekly meeting time w3c/distributed-tracing-wg#41 (6 comments by @danielkhan, @MrAlias, @mtwo, @SergeyKanzhelev, @subvocal)
-
Rename the correlation-context repo to baggage w3c/distributed-tracing-wg#42 (3 comments by @danielkhan, @plehegar)
-
Participants
-
2 participants joined.
-
Dimitar Georgievski (Wiley) joined.
-
Anton Leskovets (Wiley) joined.
-
-
1 organization joined.
-
Wiley joined.
-
GitHub
w3c/trace-context
-
1 issue opened.
-
What's the recommended guideline for generating parent-id? w3c/trace-context#412, by @prakashjmsft.
-
-
2 issues closed.
-
Document rationale for 255 leading spaces in tracestate values or remove it w3c/trace-context#409.
-
Fix numbering/level in rendered spec w3c/trace-context#403.
-
-
4 issues received 14 new comments.
-
Can the intelligence-free nature of ids be confirmed or audited by external parties? w3c/trace-context#394 (6 comments by @anuraaga, @danielkhan, @dyladan, @yurishkuro)
-
What's the recommended guideline for generating parent-id? w3c/trace-context#412 (4 comments by @dyladan, @justinfoote, @yurishkuro)
-
Document rationale for 255 leading spaces in tracestate values or remove it w3c/trace-context#409 (3 comments by @anuraaga, @dyladan)
-
How multiple APMs in a process can "collaborate" on a given trace-context? w3c/trace-context#335 (1 comment by @untitaker)
-
-
1 pull request opened.
-
Clarify description of tracestate value w3c/trace-context#411, by @anuraaga.
-
-
3 pull requests merged.
-
Clarify description of tracestate value w3c/trace-context#411.
-
Fixes wrong headline level of tracestate Header Field Values w3c/trace-context#404.
-
Update the status of the document in readme w3c/trace-context#402.
-
-
1 pull request reopened.
-
Fixes wrong headline level of tracestate Header Field Values w3c/trace-context#404, by @danielkhan.
-
-
2 pull requests received 31 new comments.
-
Clarify description of tracestate value w3c/trace-context#411 (28 comments by @anuraaga, @arminru, @codefromthecrypt, @danielkhan, @dyladan, @yurishkuro)
-
Fixes wrong headline level of tracestate Header Field Values w3c/trace-context#404 (3 comments by @danielkhan, @SergeyKanzhelev)
-
w3c/distributed-tracing-wg
-
1 pull request opened.
-
Adds an explainer document w3c/distributed-tracing-wg#40, by @danielkhan.
-
-
1 pull request merged.
-
Adds an explainer document w3c/distributed-tracing-wg#40.
-
-
1 pull request reopened.
-
Adds an explainer document w3c/distributed-tracing-wg#40, by @danielkhan.
-
-
1 pull request received 10 new comments.
-
Adds an explainer document w3c/distributed-tracing-wg#40 (10 comments by @danielkhan, @dyladan, @subvocal)
-
w3c/baggage
-
1 issue opened.
-
Review / update rationale w3c/baggage#26, by @danielkhan.
-
-
2 issues closed.
-
Use simple value format w3c/baggage#18.
-
-
2 issues received 6 new comments.
-
Rename the header to Baggage w3c/baggage#17 (3 comments by @codefromthecrypt, @danielkhan, @plehegar)
-
Consider renaming the header from Correlation-Context to correlationcontext w3c/baggage#13 (3 comments by @danielkhan, @dyladan, @yurishkuro)
-
-
1 pull request merged.
-
Add normative wording and use set-cookie value format w3c/baggage#20.
-
-
1 pull request closed.
-
Rename header from Correlation-Context to correlationcontext w3c/baggage#14.
-
-
2 pull requests received 9 new comments.
-
Add normative wording and use set-cookie value format w3c/baggage#20 (8 comments by @danielkhan, @dyladan, @mtwo)
-
Rename header from Correlation-Context to correlationcontext w3c/baggage#14 (1 comment by @danielkhan)
-
Lifecycle
-
1 charter extension.
-
Charter extended until 30 June 2020.
-
Participants
-
2 participants joined.
-
Kanwaldeep Dang (Microsoft Corporation) joined.
-
Sergey Kanzhelev (Google LLC) joined.
-
-
1 participant left.
-
Sergey Kanzhelev (Google LLC) left.
-
GitHub
w3c/trace-context
-
1 issue opened.
-
Document rationale for 255 leading spaces in tracestate values or remove it w3c/trace-context#409, by @codefromthecrypt.
-
-
3 issues received 7 new comments.
-
Document rationale for 255 leading spaces in tracestate values or remove it w3c/trace-context#409 (4 comments by @codefromthecrypt, @dyladan, @reyang)
-
Can the intelligence-free nature of ids be confirmed or audited by external parties? w3c/trace-context#394 (2 comments by @mtwo, @npdoty)
-
-
1 pull request opened.
-
Add Go to the list of implementations for Instana w3c/trace-context#410, by @andrewslotin.
-
-
3 pull requests merged.
-
Switch to Level 2 w3c/trace-context#391.
-
Clarifies the ABNF on tracestate keys w3c/trace-context#386.
-
Add Go to the list of implementations for Instana w3c/trace-context#410.
-
-
4 pull requests received 14 new comments.
-
Add Go to the list of implementations for Instana w3c/trace-context#410 (6 comments by @andrewslotin, @dyladan, @mtwo)
-
Clarifies the ABNF on tracestate keys w3c/trace-context#386 (6 comments by @codefromthecrypt, @dyladan, @justinfoote)
-
Fixes wrong headline level of tracestate Header Field Values w3c/trace-context#404 (1 comment by @arminru)
-
w3c/distributed-tracing-wg
-
1 issue opened.
-
charter: mark internal review snapshot as obsolete. w3c/distributed-tracing-wg#39, by @samuelweiler.
-
-
2 issues received 6 new comments.
-
charter: plan for getting user consent w3c/distributed-tracing-wg#36 (5 comments by @plehegar, @samuelweiler, @yurishkuro)
-
charter: clarify if/how/when this touches browsers and users w3c/distributed-tracing-wg#35 (1 comment by @plehegar)
-
-
2 pull requests opened.
-
Proposed privacy text from #36 w3c/distributed-tracing-wg#38, by @plehegar.
-
Add clearer description for Trace Context, including on the privacy s… w3c/distributed-tracing-wg#37, by @plehegar.
-
-
2 pull requests merged.
-
Proposed privacy text from #36 w3c/distributed-tracing-wg#38.
-
Add clearer description for Trace Context, including on the privacy s… w3c/distributed-tracing-wg#37.
-
w3c/baggage
-
3 issues opened.
-
Add rationale for why libraries MAY propagate or otherwise change to MUST w3c/baggage#25, by @anuraaga.
-
revert arbitrary "cookie" rationale w3c/baggage#22, by @codefromthecrypt.
-
-
1 issue closed.
-
3 issues received 9 new comments.
-
Add rationale for why libraries MAY propagate or otherwise change to MUST w3c/baggage#25 (5 comments by @anuraaga, @codefromthecrypt, @dyladan, @justinfoote)
-
revert arbitrary "cookie" rationale w3c/baggage#22 (3 comments by @codefromthecrypt, @dyladan, @SergeyKanzhelev)
-
Document rationale for 255 leading spaces in tracestate values or remove it w3c/baggage#23 (1 comment by @codefromthecrypt)
-
-
1 pull request opened.
-
Fix typo: are allows -> are allowed w3c/baggage#24, by @anuraaga.
-
-
1 pull request merged.
-
Fix typo: are allows -> are allowed w3c/baggage#24.
-
GitHub
w3c/distributed-tracing-wg
-
3 issues opened.
-
charter: plan for getting user consent w3c/distributed-tracing-wg#36, by @samuelweiler.
-
charter: clarify if/how/when this touches browsers and users w3c/distributed-tracing-wg#35, by @samuelweiler.
-
charter: fix or remove broken links to docs w3c/distributed-tracing-wg#34, by @samuelweiler.
-
-
1 issue closed.
-
charter: fix or remove broken links to docs w3c/distributed-tracing-wg#34.
-
-
2 issues received 3 new comments.
-
charter: clarify if/how/when this touches browsers and users w3c/distributed-tracing-wg#35 (1 comment by @samuelweiler)
-
1 pull request merged.
-
Feedback from March virtual meeting w3c/distributed-tracing-wg#32.
-
w3c/baggage
-
1 issue opened.
-
remove Latest published version header w3c/baggage#21, by @samuelweiler.
-
-
2 issues received 9 new comments.
-
Rename the header to Baggage w3c/baggage#17 (8 comments by @basvanbeek, @codefromthecrypt, @jcchavezs, @mtwo, @SergeyKanzhelev, @tedsuo)
-
Consider renaming the header from Correlation-Context to correlationcontext w3c/baggage#13 (1 comment by @SergeyKanzhelev)
-
-
1 pull request received 3 new comments.
w3c/trace-context
-
3 issues received 3 new comments.
-
Be consistent with normative / non-normative sections w3c/trace-context#396 (1 comment by @plehegar)
-
Can the intelligence-free nature of ids be confirmed or audited by external parties? w3c/trace-context#394 (1 comment by @plehegar)
-
1 pull request opened.
-
add new relic to list of implementations w3c/trace-context#408, by @grahamfuller1.
-
-
1 pull request merged.
-
add new relic to list of implementations w3c/trace-context#408.
-
GitHub
w3c/baggage
-
2 issues opened.
-
Use simple value format w3c/baggage#18, by @danielkhan.
-
Rename the header to Baggage w3c/baggage#17, by @SergeyKanzhelev.
-
-
3 issues closed.
-
Consider using dictionary spec for the value w3c/baggage#15.
-
Correlation Context Should be Split w3c/baggage#6.
-
Support for a type property of a Correlation Context value w3c/baggage#3.
-
-
7 issues received 35 new comments.
-
Rename the header to Baggage w3c/baggage#17 (19 comments by @codefromthecrypt, @discostu105, @dyladan, @JonathanMace, @mtwo, @mwear, @rfonseca, @SergeyKanzhelev, @shakuzen, @tedsuo, @yurishkuro)
-
Consider renaming the header from Correlation-Context to correlationcontext w3c/baggage#13 (10 comments by @codefromthecrypt, @dyladan, @felixbarny, @mtwo, @nicmunroe, @SergeyKanzhelev)
-
Support for a type property of a Correlation Context value w3c/baggage#3 (1 comment by @SergeyKanzhelev)
-
-
2 pull requests opened.
-
Add normative wording and use set-cookie value format w3c/baggage#20, by @danielkhan.
-
Add a version and further specification of value format w3c/baggage#19, by @danielkhan.
-
-
1 pull request closed.
-
Add a version and further specification of value format w3c/baggage#19.
-
-
2 pull requests received 35 new comments.
-
Add normative wording and use set-cookie value format w3c/baggage#20 (25 comments by @danielkhan, @dyladan, @yurishkuro)
-
Add a version and further specification of value format w3c/baggage#19 (10 comments by @danielkhan, @dyladan, @SergeyKanzhelev, @yurishkuro)
-
w3c/trace-context
-
15 issues opened.
-
Clarify use of trace-id in response header w3c/trace-context#407, by @dyladan.
-
Remove proposed-parent-id from response header w3c/trace-context#406, by @dyladan.
-
Requirements for CORS safe-list w3c/trace-context#405, by @dyladan.
-
Fix numbering/level in rendered spec w3c/trace-context#403, by @danielkhan.
-
Make initial traceparent optional w3c/trace-context#401, by @codefromthecrypt.
-
[response header] Representing optional fields w3c/trace-context#400, by @dyladan.
-
[response header] Representing server span ID vs proposed parent ID w3c/trace-context#399, by @dyladan.
-
Should response header fields be optional? w3c/trace-context#398, by @dyladan.
-
Be consistent with normative / non-normative sections w3c/trace-context#396, by @danielkhan.
-
Can the intelligence-free nature of ids be confirmed or audited by external parties? w3c/trace-context#394, by @danielkhan.
-
Privacy: What information may be revealed? w3c/trace-context#393, by @danielkhan.
-
Define the intended implementer w3c/trace-context#392, by @danielkhan.
-
Bogus trace and parent IDs when not sampling w3c/trace-context#390, by @basti1302.
-
W3C Trace Context only support HTTP protocol？ w3c/trace-context#389, by @Lovnx.
-
Stop using vendor terminology w3c/trace-context#387, by @codefromthecrypt.
-
-
14 issues closed.
-
[response header] Representing server span ID vs proposed parent ID w3c/trace-context#399.
-
Discourage vendors from validating other vendors' tracestate entries w3c/trace-context#384.
-
Unused file in spec directory w3c/trace-context#363.
-
Create a first draft of a response header spec w3c/trace-context#361.
-
Clarify: Should be the 32 list item limit be part of limits? w3c/trace-context#343.
-
Edit 'Sampled Flag' section to be more concise. w3c/trace-context#303.
-
Should implementation propagate flag it doesn't know about w3c/trace-context#296.
-
Remove description on how to fill up shorter trace-ids w3c/trace-context#262.
-
Should services in forward mode parse headers? w3c/trace-context#251.
-
Integrate Timing Information in Trace-Context w3c/trace-context#149.
-
Investigate Server-Timing for passing back response headers w3c/trace-context#69.
-
Fix grammar in higher-version flags parsing w3c/trace-context#368.
-
W3C Trace Context only support HTTP protocol？ w3c/trace-context#389.
-
-
22 issues received 39 new comments.
-
[response header] Representing server span ID vs proposed parent ID w3c/trace-context#399 (6 comments by @codefromthecrypt, @dyladan, @yurishkuro)
-
Remove proposed-parent-id from response header w3c/trace-context#406 (4 comments by @dyladan, @yurishkuro)
-
Clarify use of trace-id in response header w3c/trace-context#407 (3 comments by @dyladan, @yurishkuro)
-
Should response header fields be optional? w3c/trace-context#398 (3 comments by @dyladan, @yurishkuro)
-
Make initial traceparent optional w3c/trace-context#401 (2 comments by @codefromthecrypt, @danielkhan)
-
Bogus trace and parent IDs when not sampling w3c/trace-context#390 (2 comments by @danielkhan, @yurishkuro)
-
Discourage vendors from validating other vendors' tracestate entries w3c/trace-context#384 (2 comments by @codefromthecrypt, @SergeyKanzhelev)
-
We mention in joint blog post that opentelemetry is a reference implementation while readme says opencensus w3c/trace-context#353 (1 comment by @danielkhan)
-
Clarify: Should be the 32 list item limit be part of limits? w3c/trace-context#343 (1 comment by @danielkhan)
-
How multiple APMs in a process can "collaborate" on a given trace-context? w3c/trace-context#335 (1 comment by @danielkhan)
-
Should implementation propagate flag it doesn't know about w3c/trace-context#296 (1 comment by @danielkhan)
-
w3c/trace-context#69 (1 comment by @danielkhan)
-
-
7 pull requests opened.
-
Fixes wrong headline level of tracestate Header Field Values w3c/trace-context#404, by @danielkhan.
-
Update the status of the document in readme w3c/trace-context#402, by @SergeyKanzhelev.
-
Add Jaeger's Java implementation w3c/trace-context#397, by @yurishkuro.
-
Fix minor typo w3c/trace-context#395, by @danielkhan.
-
Switch to Level 2 w3c/trace-context#391, by @plehegar.
-
List Instana's current implementation w3c/trace-context#388, by @mmanciop.
-
Clarifies the ABNF on tracestate keys w3c/trace-context#386, by @codefromthecrypt.
-
-
5 pull requests merged.
-
Add Jaeger's Java implementation w3c/trace-context#397.
-
Add response headers w3c/trace-context#365.
-
Fix minor typo w3c/trace-context#395.
-
List Instana's current implementation w3c/trace-context#388.
-
Minor grammar fix w3c/trace-context#376.
-
-
8 pull requests received 38 new comments.
-
Clarifies the ABNF on tracestate keys w3c/trace-context#386 (12 comments by @basti1302, @codefromthecrypt, @danielkhan, @discostu105, @felixbarny, @Oberon00, @SergeyKanzhelev, @yurishkuro)
-
Add response headers w3c/trace-context#365 (12 comments by @codefromthecrypt, @dyladan, @yurishkuro)
-
w3c/distributed-tracing-wg
-
4 issues opened.
-
March 2020 Online Workshop Notes w3c/distributed-tracing-wg#33, by @dyladan.
-
Review the charter w3c/distributed-tracing-wg#31, by @danielkhan.
-
Create structure for guides in /docs w3c/distributed-tracing-wg#29, by @danielkhan.
-
Expected Completion dates w3c/distributed-tracing-wg#27, by @plehegar.
-
-
2 issues closed.
-
March 2020 Online Workshop Notes w3c/distributed-tracing-wg#33.
-
Review the charter w3c/distributed-tracing-wg#31.
-
-
3 issues received 3 new comments.
-
Add an example of how tracestate will be used w3c/distributed-tracing-wg#30 (1 comment by @danielkhan)
-
-
1 pull request opened.
-
Feedback from March virtual meeting w3c/distributed-tracing-wg#32, by @plehegar.
-
w3c/tracestate-ids-registry
-
1 issue opened.
-
New id: "in" (Instana) w3c/tracestate-ids-registry#4, by @mmanciop.
-
-
2 pull requests opened.
-
replace specification with company or implementor url w3c/tracestate-ids-registry#6, by @dyladan.
-
Add the `in` prefix for Instana w3c/tracestate-ids-registry#5, by @mmanciop.
-
TR publications
-
1 document published.
-
Trace Context - Level 1 published as a Recommendation. History of Trace Context - Level 1
-
Participants
-
4 participants joined.
-
Armin Ruech (Dynatrace LLC) joined.
-
Michael Kopp (Dynatrace LLC) joined.
-
Justin Foote (New Relic, Inc.) joined.
-
Tyler Yahn (New Relic, Inc.) joined.
-
GitHub
w3c/baggage
-
2 issues opened.
-
OpenTelemetry and Correlation Context w3c/baggage#16, by @mwear.
-
Consider using dictionary spec for the value w3c/baggage#15, by @SergeyKanzhelev.
-
-
3 issues received 11 new comments.
-
OpenTelemetry and Correlation Context w3c/baggage#16 (6 comments by @codefromthecrypt, @danielkhan, @dyladan, @mwear)
-
Consider using dictionary spec for the value w3c/baggage#15 (4 comments by @dyladan, @mwear, @SergeyKanzhelev)
-
w3c/trace-context
-
2 issues opened.
-
Should span annotations be supported? w3c/trace-context#385, by @deafgoat.
-
Discourage vendors from validating other vendors' tracestate entries w3c/trace-context#384, by @justinfoote.
-
-
2 issues closed.
-
Should span annotations be supported? w3c/trace-context#385.
-
Remove duplicate "the" in section 8.4 w3c/trace-context#378.
-
-
2 issues received 5 new comments.
-
Should span annotations be supported? w3c/trace-context#385 (3 comments by @deafgoat, @SergeyKanzhelev)
-
Discourage vendors from validating other vendors' tracestate entries w3c/trace-context#384 (2 comments by @dyladan, @justinfoote)
-
-
2 pull requests opened.
-
fix link to travis since we show the status w3c/trace-context#383, by @SergeyKanzhelev.
-
Errata page for Trace Context Level 1 w3c/trace-context#382, by @plehegar.
-
-
4 pull requests merged.
-
fix link to travis since we show the status w3c/trace-context#383.
-
Editorial: Update reference list link w3c/trace-context#375.
-
Errata page for Trace Context Level 1 w3c/trace-context#382.
-
remove duplicate the w3c/trace-context#381.
-
-
1 pull request received 5 new comments.
-
Add response headers w3c/trace-context#365 (5 comments by @codefromthecrypt, @dyladan, @SergeyKanzhelev)
-
Participants
-
1 participant left.
-
Bogdan Drutu (Google LLC) left.
-
GitHub
w3c/trace-context
-
3 issues opened.
-
Clarify the requirements of short `trace-id` in section 8.4 w3c/trace-context#379, by @justinfoote.
-
Remove duplicate "the" in section 8.4 w3c/trace-context#378, by @orthoplex64.
-
Test report? w3c/trace-context#373, by @astearns.
-
-
4 issues closed.
-
Clarify the requirements of short `trace-id` in section 8.4 w3c/trace-context#379.
-
Use consistent notation in section 3.2.2.1 w3c/trace-context#367.
-
Test report? w3c/trace-context#373.
-
Wording in 4.2.2 is unclear w3c/trace-context#347.
-
-
3 issues received 13 new comments.
-
Clarify the requirements of short `trace-id` in section 8.4 w3c/trace-context#379 (7 comments by @dyladan, @justinfoote, @SergeyKanzhelev)
-
-
6 pull requests opened.
-
remove duplicate the w3c/trace-context#381, by @dyladan.
-
Clarify non-normative short trace-id considerations in section 8.4 w3c/trace-context#380, by @justinfoote.
-
use consistent notation w3c/trace-context#377, by @dyladan.
-
Minor grammar fix w3c/trace-context#376, by @dyladan.
-
Editorial: Update reference list link w3c/trace-context#375, by @danielkhan.
-
Update 20-http_header_format.md tracestate Value Section w3c/trace-context#374, by @MrAlias.
-
-
4 pull requests merged.
-
use consistent notation w3c/trace-context#377.
-
Clarify wording when no traceparent is received w3c/trace-context#359.
-
Update 20-http_header_format.md tracestate Value Section w3c/trace-context#374.
-
move header format rationale to root w3c/trace-context#370.
-
-
1 pull request closed.
-
Clarify non-normative short trace-id considerations in section 8.4 w3c/trace-context#380.
-
-
5 pull requests received 26 new comments.
-
Add response headers w3c/trace-context#365 (14 comments by @cce, @dyladan, @justinfoote, @yurishkuro)
-
Minor grammar fix w3c/trace-context#376 (7 comments by @dyladan, @mtwo, @SergeyKanzhelev, @yurishkuro)
-
Clarify non-normative short trace-id considerations in section 8.4 w3c/trace-context#380 (2 comments by @dyladan, @justinfoote)
-
Update 20-http_header_format.md tracestate Value Section w3c/trace-context#374 (2 comments by @dontcallmedom, @MrAlias)
-
w3c/baggage
-
1 issue received 2 new comments.
-
Consider renaming the header from Correlation-Context to correlationcontext w3c/baggage#13 (2 comments by @dyladan, @mwear)
-