-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Azure monitor exporter authentication #32163
Labels
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This was referenced Apr 9, 2024
No it does not. This is what is currently possible. My post is about asking for a better alternative. |
This was referenced Jun 2, 2024
This was referenced Jun 10, 2024
This was referenced Jun 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component(s)
exporter/azuremonitor
Is your feature request related to a problem? Please describe.
The current implementation of the Azure monitor exporter does not support EntraID based authentication out of the box. So, One has to use aad-auth-proxy along with OTel. This additional tool adds a bit of maintenance overhead.
Describe the solution you'd like
Are there any plans to add support for EntraID based auth in the future?
If not, can the exporter use an HTTP client created using the confighttp package instead of a default HTTP client? A lot of other exporters seem to be doing this. This will allow us to create an auth extension with the capabilities of aad-auth-proxy. I think a lot of users would prefer using an extension instead of deploying a whole other tool.
Describe alternatives you've considered
No response
Additional context
The
confighttp
's HTTP client can be injected somewhere here perhapsopentelemetry-collector-contrib/exporter/azuremonitorexporter/factory.go
Lines 128 to 132 in 886c4b4
The text was updated successfully, but these errors were encountered: