-
Notifications
You must be signed in to change notification settings - Fork 27
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
Can this exporter support azure batch API for getting metrics , if not in future releases can we expect this feature? #70
Comments
@jkroepke Kindly update any updates on this issue and kindly ask any additional details required for this issue |
Hi @tharun2258 is an reason mention me? I'm not an maintainer here. |
@mblaschke The quest may solve some Rate limit issues that exists with azure-metrics-exports. The batch API is already availble, but not in armmonitor SDK package. Instead there is an dedicated monitor/azquery package which seems to be optimized for fetching metrics. https://github.com/Azure/azure-sdk-for-go/tree/main/sdk/monitor/azquery. |
Hi , Okay thanks for the reference link and information shared. |
We are currently using Azure Metric Exporter (Prometheus exporter), which is now part of Grafana agent for scraping Azure resource metrics. The Azure metric exporter is mainly based on Azure monitor REST API, which has a throttling limit of 12,000 per principal id and per subscription. Recently, Microsoft introduced the Batch API (Data Plane API), which has a throttling limit of 360,000. They recommend switching to the Batch API from the REST API (links provided below). Do you have any plans to incorporate the Batch API in Azure Metric Exporter? If so, could you please provide a high-level timeline?" Reference links: |
Reference API :
POST /subscriptions//metrics:getBatch?metricNamespace=&api-version=2023-03-01-preview
Microsoft documentation for batch API to get metrics:
https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/migrate-to-batch-api
The text was updated successfully, but these errors were encountered: