opentelemetry-dotnet icon indicating copy to clipboard operation
opentelemetry-dotnet copied to clipboard

Published 20 hours ago • verified publisher icon open-telemetry

How can I set a custom HttpMessageHandler for the underlying gRPC request on OtlpTraceExporter (netstandard2.1)

Open alexbrina opened this issue 3 years ago • 2 comments

Hi, I have setup an on-prem Elastic stack (elasticsearch + apm-server + kibana) and configured secure communication between elastic services. For convenience all server certificates are self-signed and were create using Elastic utility scripts.

Now for my application to communicate with this apm-server I need to define a custom HttpMessageHandler so I can bypass CA verification, as I won't be able to install the generated CA.crt as Trusted Root Certificate in all deployment servers.

I see that gRPC itself have an option for passing custom handler but I couldn't find a way to set it through oltp exporter options. Is it possible? Any sugestion on how to overcome this limitation?

alexbrina avatar Jul 05 '21 21:07 alexbrina