Reputation: 11
High Priority: Azure Custom Log Search Not Working in West Europe Region
Unable to use "traces" table as target for Azure Custom Log Search alert query.
When the scope is set to Azure application insights and targeted "traces" table, throws an error.
The same query running fine while running in the Log analytics editor
If I target tables related to Log Analytics it is working fine.
Note: For the alerts configured last week, whenever failure threshold met, alert triggered as it should. Facing this issue while editing the existing alerts or creating a new one.
Resources Region: WEST EUROPE
Tested another POC in SOUTH INDIA region and working fine. Able to edit/create.
Update
Existing alert failure details: (Simply clicked "Edit" > into the edit mode > "Review+Save" > Error)
Is anyone else facing the same issue?
Upvotes: 0
Views: 42
Answers (0)
Related Questions
- Azure Monitor Custom log search Query - understanding Period and Frequency
- How to Dynamically Integrate Azure Log Analytics Workspace-based Alerts with Corresponding Application Insights Traces?
- Sent the Postgresql query result to Log Analytics workspace to create custom metric in Azure Monitor
- az provider register --namespace Microsoft.EventGrid silently fails
- How to move an Azure resource from one region to another region
- Azure Function in South UK timeout when communicating with service bus in West US
- create Azure VM cannot select "europe"
- Azure - Deploy alert rules with ARM template with Metric Measurement parameter (Not Result count)
- Azure Monitor alert cross-resource log search error
- Azure Resource Manger - Microsoft.Storage/storageAccounts vs microsoft.classicstorage/storageAccounts