This repository is associated with the Distributed Tracing Working Group. It is used to work on the group's charter and processes, and as an archive of meeting notes.
This is why you should join this working group.
Specification for distributed tracing context propagation format:
- Trace Context
Report.
Status: First Public Working
Draft.
- Rationale document
- Github Repo
- Changes are tracked on GitHub, communicated in meetings and e-mails distribution list.
- Correlation Context
Report.
Status: initial draft.
- Rationale document
- Working group charter (as of working group creation). Live charter document.
- Original community group.
Overview of team related communication channels:
- GitHub issues for any specification related issues.
- Mailing List for general discussions. Please subscribe to public-trace-context@w3.org.
- Gitter Channel to reach the team: TraceContext/Lobby.
- Public Google calendar for all meetings and events Google Calendar.
- Recordings of previous meetings can be found here
We appreciate feedback and contributions. Please make sure to read rationale documents when you have a question about particular decision made in specification.
This specification defines formats to pass trace context information across systems. Our goal is to share this with the community so that various tracing and diagnostics products can operate together.
- If this becomes popular, frameworks and other services will automatically pass trace IDs through for correlated requests. This would prevent traces from hitting dead ends when a request reaches an un-instrumented service.
- Once aligned on a header name, we can ask for a CORS exception from the W3C. This would allow browsers to attach trace IDs to requests and submit tracing data to a distributed tracing service.
- Loggers can reliably parse trace / span IDs and include them in logs for correlation purposes.
- Customers can use multiple tracing solutions (Zipkin + New Relic) at the same time and not have to worry about propagating two sets of context headers.
- Frameworks can bless access to the trace context even if they prevent access to underlying request headers, making it available by default.
See Contributing.md for details.