-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Page feedback]: Add example of configuring receivers for TLS #5853
Comments
Thanks for raising these issues, @jcranfordbeyondtrust! We appreciate the detailed and constructive feedback. @open-telemetry/collector-approvers, PTAL. Thanks. |
Here's the Collector documentation page with this: We have this in the documentation page from this report: otlp/jaeger:
endpoint: jaeger-server:4317
tls:
cert_file: cert.pem
key_file: cert-key.pem The counterpart on the receiver side would be this: otlp:
protocols:
grpc:
endpoint: 0.0.0.0:4317
tls:
cert_file: cert.pem
key_file: cert-key.pem
http:
endpoint: 0.0.0.0:4318 |
Thanks, @jpkrohling! To spell out the solution to this issue, we should add this text:
just after line 292 on the Collector Configuration page. |
Closes open-telemetry#5853 Signed-off-by: Swapnil Kulkarni <[email protected]>
@tiffany76 Is this issue still open? |
Hi @pratik-mahalle, thanks for your interest. This issue is resolved and therefore closed. Please take a look through our open issues if you'd like to contribute. |
URL
https://opentelemetry.io/docs/collector/configuration/#setting-up-certificates
Description
Include example of how to configure receivers for TLS.
I see examples for exporters but not receivers.
The text was updated successfully, but these errors were encountered: