Add specs on Propagator API. (#147)
* Add specs on Propagator API. Fixes #72. * Fix a bracket. * Update TOC.
This commit is contained in:
parent
3b937909ec
commit
897afc8d05
|
|
@ -227,6 +227,15 @@ for an example.
|
||||||
**TODO**: Better describe the difference between the resource and a Node
|
**TODO**: Better describe the difference between the resource and a Node
|
||||||
https://github.com/open-telemetry/opentelemetry-proto/issues/17
|
https://github.com/open-telemetry/opentelemetry-proto/issues/17
|
||||||
|
|
||||||
|
## Propagators
|
||||||
|
|
||||||
|
OpenTelemetry uses `Propagators` to serialize and deserialize `SpanContext` and `DistributedContext`
|
||||||
|
into a binary or text format. Currently there are two types of propagators:
|
||||||
|
|
||||||
|
- `BinaryFormat` which is used to serialize and deserialize a value into a binary representation.
|
||||||
|
- `HTTPTextFormat` which is used to inject and extract a value as text into carriers that travel
|
||||||
|
in-band across process boundaries.
|
||||||
|
|
||||||
## Agent/Collector
|
## Agent/Collector
|
||||||
|
|
||||||
The OpenTelemetry service is a set of components that can collect traces,
|
The OpenTelemetry service is a set of components that can collect traces,
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue