Trace Context Level 2

W3C Editor's Draft 01

More details about this document
This version:
https://w3c.github.io/trace-context/
Latest published version:
https://www.w3.org/TR/trace-context-2/
Latest editor's draft:
https://w3c.github.io/trace-context/
History:
https://www.w3.org/standards/history/trace-context-2
Commit history
Implementation report:
https://github.com/w3c/trace-context/#reference-implementations
Editors:
Sergey Kanzhelev ( Google )
Daniel Dyla ( Dynatrace )
Yuri Shkuro ( Facebook )
Former editors:
Nik Molnar ( Microsoft )
Alois Reitbauer ( Dynatrace )
Morgan McLean ( Google )
Bogdan Drutu ( Google )
Daniel Khan ( Dynatrace )
Feedback:
GitHub w3c/trace-context ( pull requests , new issue , open issues )
public-trace-context@w3.org with subject line trace-context ( archives )
Discussions
We are on Slack.

Copyright © 2022 W3C ® ( MIT , ERCIM , Keio , Beihang ). W3C liability , trademark and permissive document license rules apply.

Abstract

Error 

Cannot
GET
/uploads/YoovIS/spec/01-abstract.md

/uploads/glCRaR/spec/01-abstract.md

Status of This Document

This is a preview

Do not attempt to implement this version of the specification. Do not reference this version as authoritative in any way. Instead, see https://w3c.github.io/trace-context/ for the Editor's draft.

This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.

Error 

Cannot
GET
/uploads/YoovIS/spec/02-sotd.md

/uploads/glCRaR/spec/02-sotd.md

This document was published by the Distributed Tracing Working Group as an Editor's Draft.

Publication as an Editor's Draft does not imply endorsement by W3C and its Members.

This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the 1 August 2017 W3C Patent Policy . W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy .

This document is governed by the 2 November 2021 W3C Process Document .

1. Conformance

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

Error 

Cannot
GET
/uploads/YoovIS/spec/10-overview.md

/uploads/glCRaR/spec/10-overview.md
Error 

Cannot
GET
/uploads/YoovIS/spec/20-http_request_header_format.md

/uploads/glCRaR/spec/20-http_request_header_format.md
Error 

Cannot
GET
/uploads/YoovIS/spec/21-http_response_header_format.md

/uploads/glCRaR/spec/21-http_response_header_format.md
Error 

Cannot
GET
/uploads/YoovIS/spec/30-processing-model.md

/uploads/glCRaR/spec/30-processing-model.md
Error 

Cannot
GET
/uploads/YoovIS/spec/40-other-protocols.md

/uploads/glCRaR/spec/40-other-protocols.md
Error 

Cannot
GET
/uploads/YoovIS/spec/50-privacy.md

/uploads/glCRaR/spec/50-privacy.md
Error 

Cannot
GET
/uploads/YoovIS/spec/51-security.md

/uploads/glCRaR/spec/51-security.md
Error 

Cannot
GET
/uploads/YoovIS/spec/60-trace-id-format.md

/uploads/glCRaR/spec/60-trace-id-format.md
Error 

Cannot
GET
/uploads/YoovIS/spec/

/uploads/glCRaR/spec/


61

-

span

-id-format
.md
Error 

Cannot
GET
/uploads/YoovIS/spec/60-acknowledgments.md

/uploads/glCRaR/spec/60-acknowledgments.md

2. Glossary

This section is non-normative.

Distributed trace
A distributed trace is a set of events, triggered as a result of a single logical operation, consolidated across various components of an application. A distributed trace contains events that cross process, network and security boundaries. A distributed trace may be initiated when someone presses a button to start an action on a website - in this example, the trace will represent calls made between the downstream services that handled the chain of requests initiated by this button being pressed.
Opaque value
An opaque value refers to a value that can only be understood or processed in any way by the distributed trace participant that generated this value. Any other participant must treat it as a blob of bytes.