telegraf agent azure output plugin does not support sovereign clouds (e.g. usgovcloud) #5452
Labels
area/azure
Azure plugins including eventhub_consumer, azure_storage_queue, azure_monitor
feature request
Requests for new plugin and for new features to existing plugins
Milestone
Feature Request
I've been using telegraf agent to ship metrics to Azure Monitor instances in multiple Azure subscriptions. It looks like the URL is hard-coded as [regionname].monitoring.azure.com which doesn't result in support of sovereign cloud environments like US Goverment (e.g.
usgovvirginia.monitoring.azure.com
is incorrect in this context, and should bemonitoring.core.usgovcloudapi.net
.)Proposal:
Allow for endpoint overrides to support the environment, with an output configuration variable to define the endpoint.
It would be even cleaner if telegraf were able to automatically determine where it was running by querying the Azure Instance Metadata service, but reviewing the available information doesn't show tenantId (which can be used to derive whether it's Azure Commercial or Government), or any other information to reveal the necessary information.
Current behavior:
telegraf attempts to send metrics to
https://<region>.monitoring.azure.com
Desired behavior:
Allow for an override for the Azure Monitor output host.
For example, the regional endpoints seem to be shunned in favor of the simpler
monitoring.core.usgovcloudapi.net
in Azure USGovernmentUse case:
Telegraf doesn't send metrics to the correct URL in non-Commercial Azure environments. Allowing for an override value that, if set, changes the output URL for metrics data POSTs, would solve this roadblock for me (and possibly other users who wish to leverage Azure Monitor in sovereign Azure cloud environments)
Microsoft does offer a method for determining the cloud environment you're operating in, via this method:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service#getting-azure-environment-where-the-vm-is-running
The text was updated successfully, but these errors were encountered: