Use http for default OTLP endpoint - #112
Merged
Merged
Conversation
The telemetry server has no TLS on the raw IP, so https connections fail. Point the default at plain http until TLS is set up.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 telemetry server currently has no TLS on the raw IP, so the default
https://OTLP endpoint fails to connect. Switch the default inreference.confto plainhttpuntil TLS is set up (e.g. Let's Encrypt behind the nginx front).Note: telemetry payloads leave users' machines unencrypted with this default — TLS should be restored before a wider release.
🤖 Generated with Claude Code