Open fiferrando opened 8 months ago
Hi,
I have un update: azure_quota_current
metric is also giving wrong results. Two files are attached to this comment:
azurerm_quota_current{scope="machinelearningservices"} * on(subscriptionID) group_left(subscriptionName) azurerm_subscription_info
azurerm_quota_limit{scope="machinelearningservices"} * on(subscriptionID) group_left(subscriptionName) azurerm_subscription_info
)The examples shown only regards quotas which name starts with standard
or Standard
.
I'm going to edit the title of the issue accordingly.
Hi,
May you please give me an update on this problem?
Thank you in advance for all the help, Best regards.
Filippo Ferrando
check the Azure REST API response via powershell, eg:
Invoke-AzRestMethod -Method GET -Uri https://management.azure.com/subscriptions/{SUBSCRIPTIONID}/providers/Microsoft.MachineLearningServices/locations/{LOCATION}/usages?api-version=2022-10-01
the Azure REST api shows following values for me in my personal subscription:
{
"unit": "Count",
"currentValue": 0,
"limit": -1,
"name": {
"value": "standardMSv2Family",
"localizedValue": "Standard MSv2 Family Cluster LowPriority vCPUs"
},
"type": "Microsoft.MachineLearningServices/vmFamily/lowPriorityCores/usages",
"id": "/subscriptions/xxxxxxxxx/usages/standardMSv2Family"
}
the exporter just shows the value from the API.
Hi,
The metric azurerm_quota_limit returns strange results, -1, with the parameters specified in the title. These limits are obviously different on Azure (0 or positives). The permission of the service principal used by the exporter is Reader on Azure management group containing all the subscriptions. An image with example comparison follows:
Thank you in advance for all the help, Best regards.
Filippo Ferrando