Skip to content
This repository has been archived by the owner on Jul 1, 2022. It is now read-only.

Commit

Permalink
Add 'w3c' to valid JAEGER_PROPAGATION options (#736)
Browse files Browse the repository at this point in the history
Signed-off-by: chgl <[email protected]>
  • Loading branch information
chgl authored Aug 17, 2020
1 parent a3bf0e3 commit 7d2a09e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion jaeger-core/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,7 @@ JAEGER_ENDPOINT | no | The traces endpoint, in case the client should connect di
JAEGER_AUTH_TOKEN | no | Authentication Token to send as "Bearer" to the endpoint
JAEGER_USER | no | Username to send as part of "Basic" authentication to the endpoint
JAEGER_PASSWORD | no | Password to send as part of "Basic" authentication to the endpoint
JAEGER_PROPAGATION | no | Comma separated list of formats to use for propagating the trace context. Defaults to the standard Jaeger format. Valid values are **jaeger** and **b3**
JAEGER_PROPAGATION | no | Comma separated list of formats to use for propagating the trace context. Defaults to the standard Jaeger format. Valid values are **jaeger**, **b3**, and **w3c**
JAEGER_REPORTER_LOG_SPANS | no | Whether the reporter should also log the spans
JAEGER_REPORTER_MAX_QUEUE_SIZE | no | The reporter's maximum queue size
JAEGER_REPORTER_FLUSH_INTERVAL | no | The reporter's flush interval (ms)
Expand Down

0 comments on commit 7d2a09e

Please sign in to comment.