[BUG] "No registered resource provider found for location 'eastus2' and API version '2018-01-01' for type 'storageAccounts/blobServices'

[gokhandegerli]

[BUG] "No registered resource provider found for location 'eastus2' and API version '2018-01-01' for type 'storageAccounts/blobServices'

[gokhandegerli]

https://learn.microsoft.com/en-us/answers/questions/1610981/trying-to-create-an-alert-by-means-of-java-sdk-or

[joshfree]

@weidongxu-microsoft could you please follow up

[weidongxu-microsoft]

@gokhandegerli

The api-version SDK sent to monitor MetricAlert should be 2018-03-01
https://github.com/Azure/azure-sdk-for-java/blob/azure-resourcemanager-monitor_2.36.0/sdk/resourcemanager/azure-resourcemanager-monitor/src/main/java/com/azure/resourcemanager/monitor/implementation/MetricAlertsClientImpl.java#L522

The api-version 2018-01-01 appears to be completely in backend implementation when it work on the storage account.

Would it possible for you to enable the logging, and share the URL and JSON request body? (redact anything that could be sensitive)?

We'd like to know whether we should ask backend to track the issue.

[gokhandegerli]

@weidongxu-microsoft

Please see below the API request details, however I do not know what you mean for enabling the logging.

PUT request URL: "https://management.azure.com/subscriptions/26e4c203-9a71-4ae0-a0e7-65dd5c086761/resourceGroups/c4c-gokhanalertestdev-qq6yviniqy/providers/Microsoft.Insights/metricAlerts/new01?api-version=2018-03-01"

JSON request body:
{
"location": "global",
"properties": {
"severity": 3,
"autoMitigate": true,
"windowSize": "PT1M",
"criteria": {
"allOf": [
{
"metricName": "BlobCount",
"timeAggregation": "AVERAGE",
"criterionType": "StaticThresholdCriterion",
"name": "y0jgd4j4f1-BlobCount01",
"threshold": 10,
"operator": "GreaterThan"
}
],
"odata.type": "Microsoft.Azure.Monitor.SingleResourceMultipleMetricCriteria",
"actions": [
{
"actionGroupId": "/subscriptions/26E4C203-9A71-4AE0-A0E7-65DD5C086761/resourceGroups/c4c-gokhanalertestdev-qq6yviniqy/providers/microsoft.insights/actionGroups/newNG01"
}
]
},
"evaluationFrequency": "PT1M",
"description": "BlobCount01",
"scopes": [
"/subscriptions/26e4c203-9a71-4ae0-a0e7-65dd5c086761/resourceGroups/c4c-gokhanalertestdev-qq6yviniqy/providers/Microsoft.Storage/storageAccounts/gokhantestc4c212ftk/blobServices/default/containersy0jgd4j4f1c4c"
],
"enabled": true
}
}

[weidongxu-microsoft]

@gokhandegerli

Thanks. The URL and payload is what we need. (logging just a way to print these)

There is nothing from SDK that specify 2018-01-01. This would be from backend (probably when it works on the storage account resource in scopes).

If you can open customer support ticket, it should be faster to handle this way, as it need to connect to backend dev to diagnose and fix.