[DOC] Fix OTLP documentation: Default endpoint is wrong for OTLP/HTTP #2560
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lalitb
approved these changes
Feb 27, 2024
ThomsonTan
approved these changes
Feb 27, 2024
marcalff
approved these changes
Feb 27, 2024
owent
approved these changes
Feb 28, 2024
Merged
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The documentation was misleading end users. The documentation says the default for
OTEL_EXPORTER_OTLP_ENDPOINTishttp://localhost:4318/v1/traces. When they want to send data to a different backend they are inclined to usehttp://my-backend:4318/v1/traceswhich will not work.