docs: improve gRPC insecure connection guidance #6215
+40
−1
Conversation
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
- Clarify that secure (TLS) connection is used by default - Add example showing http:// scheme for insecure connections - Add example with explicit insecure credentials configuration - Update documentation to better guide local development setup
|
|
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.
Which problem is this PR solving?
When connecting the gRPC exporter to a local OTLP collector (e.g., Phoenix, Jaeger) without TLS, developers encounter errors like:
The README states "By default, plaintext connection is used" (line 47), which is outdated since v0.29.0. The exporter now defaults to secure connections, but there's no clear guidance on using insecure connections for local development.
Short description of the changes
http://URL scheme (recommended, simpler)credentials.createInsecure()(alternative)Type of change
Checklist: