Switch API preference for Log Alerts
Published date: 01 May, 2019
Until recently, you managed alert rules in the Microsoft Operations Management Suite portal. The new alerts experience was integrated with various services in Microsoft Azure, including Log Analytics, and we asked to extend your alert rules from OMS portal to Azure. But to ensure minimal disruption for customers, the process did not alter the programmatic interface for its consumption – Log Analytics Alert API based on SavedSearch.
But now you announce a true Azure programmatic alternative for Log Analytics alerting users, Azure Monitor – ScheduledQueryRules API, which is also reflective in your Azure billing – for log alerts. To learn more about how to manage your log alerts using the scheduledQueryRules API, see Managing log alerts using Azure Resource Template and Managing log alerts using PowerShell, CLI or API.
Switching to ScheduledQueryRules API
Currently, by default in Azure portal, the legacy Log Analytics Alert API is used for creating and managing new log alert rules. Customers can now instead change their preference to use ScheduledQueryRules API without disruption to their monitoring by following some simple steps, detailed here. And gain many benefits and functionalities such as using cross-resource queries in log alert rule, fetching up to 48 hours of data in alert query, having access to all future improvements in log alert rules and more.
From 1 June 2019, any new Log Analytics workspace created in Azure public cloud will start to use ScheduledQueryRules API for log alert rule creation and management in Azure portal. Additionally, the best practices for queries in log alert rules will also be enforced via log alert API interfaces from 1 June 2019.