How to add client TLS in the OpenTelemetryRumInitializer?

[brsgina]

Hi,

I am using the OpenTelemetryRumInitializer.initialize function in my Android project to create the OpenTelemetryRum instance and I would like to set a client TLS. With io.opentelemetry.android.instrumentation (+ io.opentelemetry.exporter.otlp) it was possible to build a OtlpHttpLogRecordExporter and set the client TLS to it with the addLoggerProviderCustomizer function:

val logExporter = OtlpHttpLogRecordExporter.builder().setEndpoint(BASE_URL).setClientTls(keyBytes, crtBytes) .build()

But if I understand correctly, there is currently no solution for this in the initializer configuration. Is there currently a way to set up a TLS certificate, or will it be possible to specify something in the configuration later?

Thank you in advance for the response!

[breedx-splk]

Hi @brsgina thanks for the inquiry. Just to be clear, we are talking about client-certs, and not just enabling TLS (any old https endpoint url will work just fine for regular TLS). It looks like we don't currently expose a way to configure client TLS in the OpenTelemetryRumInitializer!

This can currently be accomplished with the OpenTelemetryRumBuilder from the core module, but it is a bit more work to configure. The Otlp*ExporterBuilder classes from the java core repos have a setClientTls() method on them.

Given that Android apps run around in the wild and the endpoints need to talk directly with the devices, I could absolutely see the desire to have client-side certs for ingest servers to be able to validate that data is coming from a trusted source. I think this is something we should add at the level of the initializer.

[brsgina]

Hi @breedx-splk , thank you for the quick response. Yes we are talking abut client-certs and yes, this would be a useful new feature :) Can you tell me approximately when or how soon I can expect a released version that already includes this configuration option?

[breedx-splk]

Hi @breedx-splk , thank you for the quick response. Yes we are talking abut client-certs and yes, this would be a useful new feature :)

😎 Cool thanks for the clarification.

Can you tell me approximately when or how soon I can expect a released version that already includes this configuration option?

Well, that's not generally how this works. It's up to the community to agree on and build the feature, so timelines are difficult to predict. We're in the holiday season now, and you can expect work to slow down considerably for a while. I have a partial implementation started, but if I'm honest it probably won't get completed until January sometime. Thanks again!