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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Service Used
Monitor
API Versions Used
2022-06-01
Description
Error details should be exposed, PR #482 only handles the case for long-running-operation.
Existing error only shows InvalidPayload: Data collection rule is invalid without any details, which looks like
Error: updating Data Collection Rule (Subscription: "<redacted>"
│ Resource Group Name: "wt-example-resources"
│ Data Collection Rule Name: "example-rule"): unexpected status 400 (400 Bad Request) with error: InvalidPayload: Data collection rule is invalid
│
│ with azurerm_monitor_data_collection_rule.example,
│ on main.tf line 120, in resource "azurerm_monitor_data_collection_rule" "example":
│ 120: resource "azurerm_monitor_data_collection_rule" "example" {
│
│ updating Data Collection Rule (Subscription: "49824ffe-67ce-4765-be73-93c2ac1b55a8"
│ Resource Group Name: "wt-example-resources"
│ Data Collection Rule Name: "example-rule"): unexpected status 400 (400 Bad Request) with error: InvalidPayload: Data collection rule is invalid
╵
but the response has more details:
{"error":{"code":"InvalidPayload","message":"Data collection rule is invalid","details":[{"code":"InvalidTransformQuery","message":"Error occurred while compiling query in query: SyntaxError:0x00000001 at 1:76 : extraneous input ',' expecting <EOF>","target":"properties.dataFlows[1]"}]}}
The text was updated successfully, but these errors were encountered:
teowa
changed the title
Issue with Monitor DataCollectionRule / API Version 2022-06-01: expose detail for error
Issue with Monitor DataCollectionRule / API Version 2022-06-01: expose error detail for non-LRO method
Dec 4, 2024
Is there an existing issue for this?
Community Note
Service Used
Monitor
API Versions Used
2022-06-01
Description
Error details should be exposed, PR #482 only handles the case for long-running-operation.
Existing error only shows
InvalidPayload: Data collection rule is invalid
without any details, which looks likebut the response has more details:
repro config
API log by using Azure CLI:
swagger has defined the error struct:
https://github.com/Azure/azure-rest-api-specs/blob/bbf2878dfeff8ee6f5a8ac6efad61c801972cfb5/specification/common-types/resource-management/v2/types.json#L285-L337
https://github.com/Azure/azure-rest-api-specs/blob/065bac6153f6a83de668f55803270bc6f31f5bc3/specification/monitor/resource-manager/Microsoft.Insights/stable/2022-06-01/dataCollectionRules_API.json#L200-L206
Maybe we should consume the swagger and generate the CustomErrorParser, but I am not sure.
References
hashicorp/terraform-provider-azurerm#27820
The text was updated successfully, but these errors were encountered: