Closed aristosvo closed 3 years ago
@ruowan Can you give us anything to assure this is in progress or anything? It's bugging my day to day an awful lot
Sorry for delay response. I will try to triage this issue to service team.
Looks like this is unique to API Version 2021-07-01-preview
- so this appears to be an API Regression
Hi, I'm experiencing issues with this as well. @tombuildsstuff , our process is calling the API as follows, which is not using the 2021-07-01-preview
API version.
PUT /subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.Insights/metricAlerts/XXXXXX?api-version=2018-03-01
@ruowan Can you give us anything to assure this is in progress or anything? It's bugging my day to day an awful lot
Agree this is a real problem, my Terraform is making a mess. Is there an ETA on resolution?
Hi, I'm experiencing issues with this as well. Our process is calling the API as follows, which is not using the 2021-07-01-preview API version.
PUT /subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.Insights/metricAlerts/XXXXXX?api-version=2018-03-01
@SudoSpartanDan We share the same problem 🤜🏽 . As visible in the logs I posted:
<url>?api-version=2018-03-01
Azure-SDK-For-Go/v56.2.0 insights/2021-07-01-preview
There is a difference between SDK version and the actual API version used, confusing the whole thing a bit.
The maintainers of the Terraform azurerm provider have noticed this issue and have a ticket open, there is a comment that confirms this is an upstream issue with the Azure API:
I tried to dig into the problem with a Microsoft support ticket and, from their testing, it seems like the newer version of the API causes this.
Hopefully Microsoft will revert this bug soon.
The maintainers of the Terraform azurerm provider have noticed this issue and have a ticket open, there is a comment that confirms this is an upstream issue with the Azure API:
I tried to dig into the problem with a Microsoft support ticket and, from their testing, it seems like the newer version of the API causes this.
Hopefully Microsoft will revert this bug soon.
Unfortunately, the ticket didn't go anywhere. :( I was told it was an issue on the Terraform side, which we can see here is not the case. Anyone else able to get some progress on this?
@ruowan There is still no-one assigned to this issue, can you take a quick look? I'd expect to see an assignment on a service team and/or some members.
Maybe it needs a different tag, like Monitor - ApplicationInsights / Monitor - LogAnalytics / Monitor - Operational Insights / Monitor - Metrics?
@ruowan This is affecting our ability to run proper reports on our resources. What do we need to do to escalate this issue? I submitted a Microsoft ticket, but it was closed because it was believed to be a Terraform issue. From our logs and the evidence presented by @aristosvo, though, this seems to be an issue with the API or the Azure SDK itself.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azmonapplicationinsights.
Author: | aristosvo |
---|---|
Assignees: | - |
Labels: | `question`, `Monitor - Operational Insights`, `Insights`, `Service Attention`, `customer-reported`, `Monitor - Metrics`, `Monitor - ApplicationInsights` |
Milestone: | - |
Sorry for inconveniency. I added monitor labels. Since I am not from monitor team. I am syncing with my manager to escalate this issue. Will respond soon.
Hi, @yashmuel could you pls take a look at this issue?
hi, @aristosvo, I'm from Metric Alerts team. We had a bug in the backend, regarding lowercase tags. We've already fixed this, can you please try again and let me know if it still reproduced?
I'll try and let you know!
@yashmuel Thanks a lot, it seems fixed! If there is any better way to provide you this feedback in the future, I'm happy to hear it.
I'll introduce some extra tests for the azurerm
Terraform provider to keep an eye on it and future regressions.
Created metric alert gets lowercase tags keys instead of uppercase as submitted:
Related