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
Add the option of enabling TLS for sending traces #12
Comments
We have this feature (and few other features) in our roadmap:
Trying to understand priorities for those. So, thank you for your interest in this module and for submitting a feature request. |
I`m also interesting to use https for collector endpoint with tls option insecure_skip_verify |
We are going to implement TLS export, but I'm not sure about 'insecure_skip_verify'. If you need such option, perhaps, you don't really need TLS. As a workaround for now you can try to use otelcol, which can accept HTTP and reexport via HTTPS. |
If I understand the problem correct, the way we've gotten around this is by doing the following:
Would that solve this use case? |
I mean, need to skip certificate verification. Because, using self signed ssl and some time there are problems, with adding these everytime. |
Is your feature request related to a problem? Please describe
We would like to enforce TLS for sending our traces. But we are not able to do it for nginx traces as
nginx-otel
does not have any config option to enable it.Describe the solution you'd like
Beeing able to specify:
Describe alternatives you've considered
None.
Additional context
None.
The text was updated successfully, but these errors were encountered: