Skip to content

Commit

Permalink
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
further smaller tweaks
Browse files Browse the repository at this point in the history
Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>
jpkrohling committed Jan 23, 2024
1 parent 36cf871 commit d104bb2
Showing 3 changed files with 7 additions and 4 deletions.
2 changes: 1 addition & 1 deletion specification/configuration/sdk-environment-variables.md
Original file line number Diff line number Diff line change
@@ -92,7 +92,7 @@ For example, the value `12000` indicates 12000 milliseconds, i.e., 12 seconds.
| OTEL_SERVICE_NAME | Sets the value of the [`service.name`](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/resource/README.md#service) resource attribute | | If `service.name` is also provided in `OTEL_RESOURCE_ATTRIBUTES`, then `OTEL_SERVICE_NAME` takes precedence. |
| OTEL_LOG_LEVEL | Log level used by the SDK logger | "info" | |
| OTEL_PROPAGATORS | Propagators to be used as a comma-separated list | "tracecontext,baggage" | Values MUST be deduplicated in order to register a `Propagator` only once. |
| OTEL_CLIENT_PROPAGATORS | Client propagators to be used as a comma-separated list | | Values MUST be deduplicated in order to register a `ClientPropagator` only once. |
| OTEL_RESPONSE_PROPAGATORS| Response propagators to be used as a comma-separated list | | Values MUST be deduplicated in order to register a `ResponsePropagator` only once. |
| OTEL_TRACES_SAMPLER | Sampler to be used for traces | "parentbased_always_on" | See [Sampling](../trace/sdk.md#sampling) |
| OTEL_TRACES_SAMPLER_ARG | String value to be used as the sampler argument | | The specified value will only be used if OTEL_TRACES_SAMPLER is set. Each Sampler type defines its own expected input, if any. Invalid or unrecognized input MUST be logged and MUST be otherwise ignored, i.e. the implementation MUST behave as if OTEL_TRACES_SAMPLER_ARG is not set. |

3 changes: 3 additions & 0 deletions specification/context/api-propagators.md
Original file line number Diff line number Diff line change
@@ -89,6 +89,9 @@ the same trace context it got from the initial document headers. This trace
context might be used as a link to/from a new trace, or might be directly reused
as the parent of new spans.

The trace context obtained from response propagators are meant to be consumed
only by the caller and shouldn't be propagated further back.

## Propagator Types

A `Propagator` type defines the restrictions imposed by a specific transport
6 changes: 3 additions & 3 deletions specification/overview.md
Original file line number Diff line number Diff line change
@@ -349,13 +349,13 @@ See the [Context](context/README.md)

## Propagators

OpenTelemetry uses `Propagators` to serialize and deserialize cross-cutting
concern values such as `Span`s (usually only the `SpanContext` portion) and
OpenTelemetry uses `Propagators` to serialize and deserialize payloads for
cross-cutting applications, such as `Span`s (usually only the `SpanContext` portion) and
`Baggage`. Different `Propagator` classes and types define the restrictions
imposed by a specific direction, transport, and are bound to a data type.

Propagators can be of one of two classes: `Propagator` (classic, forward), or
`ClientPropagator` (backward). See [Propagator
`ResponsePropagator` (backward). See [Propagator
Classes](context/api-propagators.md#propagator-classes).

The Propagators API currently defines one `Propagator` type:

0 comments on commit d104bb2

Please sign in to comment.