Tweak OpenTelemetry config to rely on default OTel SDK env vars #108
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR builds on #92 by tweaking how OpenTelemtry is configured. This removes
$BRIOCHE_JAEGER_ENDPOINT
completely, and instead adds a new$BRIOCHE_ENABLE_OTEL
env var. When$BRIOCHE_ENABLE_OTEL=1
, then it will use the default OpenTelemtry SDK config to pick the endpoint and URL, see https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/#otel_exporter_otlp_protocolPreviously, this command from #92 (comment):
...would now become this: