Support all configuration of otlp exporter

[TommyCpp]

Add support for all configurations in spec

• Endpoint (OTLP/HTTP)
  - It was partially supported with Add signal path automatically for OTLP HTTP exporter #773 missing
• Endpoint (OTLP/gRPC)
• Insecure
• Certificate File
• Client key file
• Client certificate file
• Headers
• Compression
• Timeout
• Protocol

[TylerHelmuth]

Does opentelemtry-otlp already add the signal path automatically when using gRPC?

[TommyCpp]

Does opentelemtry-otlp already add the signal path automatically when using gRPC?

gRPC doesn't really require a path, right? The service/client stub should take care of that

[TylerHelmuth]

You're totally right, my bad

[atanunq]

Hey all! I'm interested in trying to implement one of the items in the list as a way to get more familiar with the repository. Certificate file looks like a good candidate. However, I am struggling with seeing the configuration flow in general. Could you please share some pointers on how to go about implementing it?

For example, I am testing locally with tonic. I managed to connect over TLS to a collector using new_exporter().tonic().with_tls_config(ClientTlsConfig::new(...)). However, this is tonic-specific. Based on the linked spec above, I assume the new way of configuring should be taken into account within all protocols (i.e different third party crates). Is that correct?

If that is the case, the ExportConfig struct looks like a good place to add it. Then, though, ExportConfig and TonicConfig.tls_config may have different values and one needs to take precedence over the other. How/where would that be decided?

I do hope any of that makes sense. Thanks!

[hdost]

Related #984