Skip to content
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

[FEATURE REQ] Support programmatic "configuration" of Azure Monitor OTel #43875

Open
2 tasks done
mmarczell-graphisoft opened this issue Jan 22, 2025 · 0 comments
Open
2 tasks done
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

Comments

@mmarczell-graphisoft
Copy link

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:

val exporter = AzureMonitorExporter.builder().setConnectionString("...")
Embrace.getInstance().addLogRecordExporter(exporter)

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

This package assumes your application is already instrumented with the OpenTelemetry SDK

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

  • Description Added
  • Expected solution specified
@github-actions github-actions bot added 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 labels Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

1 participant