Skip to content

Issues: w3c/trace-context

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

30 Open 204 Closed
30 Open 204 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Question about tracecontext in load-balancer scenarios
#575 opened Oct 4, 2024 by kalyanaj
1
Trace Context Extensibility
#573 opened May 7, 2024 by dyladan
11
Can Traceresponse enable parent-child relationship between browser and server spans?
#572 opened Apr 30, 2024 by scheler
@dyladan
Remove all markdown includes
#562 opened Mar 26, 2024 by dyladan
Server-timing names
#561 opened Feb 27, 2024 by SergeyKanzhelev
6
Revisit header name -- Server-Timing vs. traceresponse
#556 opened Jan 10, 2024 by jpkrohling
10
Should tracing headers be included in 304 Not Modified responses?
#554 opened Nov 13, 2023 by mitar
14
Proposal: Allow common base64 encoding in tracestate values
#551 opened Nov 2, 2023 by feldentm-SAP
5
Proposal: Add a "propagation-only-parent" flag to be set to true if parents is a no-tracing service trace-context-level-3
#550 opened Nov 1, 2023 by bogdandrutu
6
Autopublishing level2/Level3 specs need to work with multiple markdown files
#545 opened Aug 29, 2023 by kalyanaj
@plehegar
2
Random part of trace ID should be uniformly distributed backport-to-level-2-required This is a PR against main that is meant to be backported to level 2.
#544 opened Jun 30, 2023 by oertl
@dyladan
3
Level 3 spec: Update privacy section to include information about traceresponse headers.
#542 opened Jun 6, 2023 by kalyanaj
@kalyanaj
Update tests to test Trace Context level 2 by default
#529 opened Apr 11, 2023 by kalyanaj
@dyladan
Trace Context: Apache Kafka protocol specification
#504 opened Oct 13, 2022 by ppatierno
5
Request to republish level-1 spec (to publish a recent editorial change)
#503 opened Oct 12, 2022 by kalyanaj
@plehegar
Enable automatic publishing for Level 2 branch
#502 opened Oct 12, 2022 by kalyanaj
@plehegar
Inconsistent text style Editorial The reported issue can be addressed with an editorial change. This tag could be combined with others
#485 opened Apr 12, 2022 by dyladan
2
tracestate response header proposal
#483 opened Mar 2, 2022 by dyladan
4
Vendor information in the response from traced service
#466 opened Sep 16, 2021 by wjch-krl
@kalyanaj
5
Consider trace context support for probability sampling
#463 opened Aug 17, 2021 by jmacd
@dyladan
2
Add "request" to glossary
#452 opened Apr 6, 2021 by SergeyKanzhelev
@kalyanaj
1
Define entry/value length/size consistently
#449 opened Jan 26, 2021 by dyladan
@dyladan
Requirements for CORS safe-list revisit-later
#405 opened Mar 27, 2020 by dyladan 8. future-work
@dyladan
3
Make initial traceparent optional revisit-later
#401 opened Mar 26, 2020 by codefromthecrypt 7. level-2
5
Be consistent with normative / non-normative sections Editorial The reported issue can be addressed with an editorial change. This tag could be combined with others privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. todo
#396 opened Mar 25, 2020 by danielkhan 7. level-2
2
ProTip! Updated in the last three days: updated:>2024-11-08.