You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our environment, we use Azure Monitor Private Link to route monitoring data through a secure private endpoint instead of the public endpoint. This setup enhances security by ensuring that all traffic remains within the Azure backbone and avoids traversing the public internet.
We want the Telegraf outputs.azure_monitor plugin to support a configurable endpoint field that allows us to specify the Private Link FQDN (e.g., https://workspace-name-east-us-monitor-xxxxx.privatelink.eastus.prometheus.monitor.azure.com), which resolves to the private endpoint via Azure Private DNS. This would simplify configuration and eliminate the need for DNS overrides or additional network proxies.
Expected behavior
When using the plugin in environments with Azure Monitor Private Link:
A new optional endpoint field (or similar) in the plugin configuration allows specifying the Private Link FQDN.
Metrics sent to the specified endpoint are routed to the private endpoint without relying on DNS changes.
The plugin seamlessly integrates with Azure Monitor Workspaces configured with Private Link.
Example Configuration:
[[outputs.azure_monitor]]
region = "eastus"
resource_id = "/subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/microsoft.monitor/workspaces/<workspace-name>"
endpoint = " https://workspace-name-east-us-monitor-xxxxx.privatelink.eastus.prometheus.monitor.azure.com" # Private DNS resolves to private endpoint
Actual behavior
Currently, the outputs.azure_monitor plugin defaults to the public endpoint (https://.monitoring.azure.com) with no option to override it for a private endpoint. This forces users to:
Modify DNS to resolve the public FQDN to the private endpoint’s IP.
Use a network proxy to route traffic to the private endpoint.
Both workarounds increase complexity and are prone to misconfiguration, particularly in secure environments where Private Link is mandated.
Additional info
No response
The text was updated successfully, but these errors were encountered:
Use Case
In our environment, we use Azure Monitor Private Link to route monitoring data through a secure private endpoint instead of the public endpoint. This setup enhances security by ensuring that all traffic remains within the Azure backbone and avoids traversing the public internet.
We want the Telegraf outputs.azure_monitor plugin to support a configurable endpoint field that allows us to specify the Private Link FQDN (e.g., https://workspace-name-east-us-monitor-xxxxx.privatelink.eastus.prometheus.monitor.azure.com), which resolves to the private endpoint via Azure Private DNS. This would simplify configuration and eliminate the need for DNS overrides or additional network proxies.
Expected behavior
When using the plugin in environments with Azure Monitor Private Link:
endpoint
field (or similar) in the plugin configuration allows specifying the Private Link FQDN.Example Configuration:
Actual behavior
Currently, the outputs.azure_monitor plugin defaults to the public endpoint (https://.monitoring.azure.com) with no option to override it for a private endpoint. This forces users to:
Both workarounds increase complexity and are prone to misconfiguration, particularly in secure environments where Private Link is mandated.
Additional info
No response
The text was updated successfully, but these errors were encountered: