[FEATURE REQ] Support programmatic "configuration" of Azure Monitor OTel #43875
Labels
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Is your feature request related to a problem? Please describe.
I would like to use the Azure Monitor OTel Exporter with an OTel SDK other than the reference implementation (specifically Embrace.io's OTel SDK for Android). The Embrace SDK does not seem to support "autoconfiguration".
Describe the solution you'd like
I would like to be able to add Azure exporters to the Embrace SDK individually. From what I understand, this requires the Azure OTel Exporter library to support manual / programmatic "configuration" in addition to "autoconfiguration".
Here's roughly what I would like to be able to do:
But the public API of the Azure Monitor OTel Exporter currently does not seem to let me directly create SpanExporter or LogRecordExporter, I can only wire things together by hooking Azure into the "autoconfiguration" step, which doesn't exist in the Embrace SDK.
Describe alternatives you've considered
Privately forking the Azure Monitor OTel library and exposing some internals.
Additional context
The Azure OTel Exporter for Java docs at https://learn.microsoft.com/en-us/java/api/overview/azure/monitor-opentelemetry-exporter-readme?view=azure-java-preview state that
It seems like a core promise of OpenTelemetry is that it's a standard and not just one implementation. I should be able to mix and match components that are standard compliant. The above assumption goes directly against that promise in this case.
Documentation on Embrace Android OTel SDK: https://embrace.io/blog/android-opentelemetry-exporter-walkthrough/
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
The text was updated successfully, but these errors were encountered: