Skip to content

Commit 34d09f1

Browse files
author
AbhishekMallick01
committed
Azure Monitor for Azure Backup - GA
1 parent 47428b6 commit 34d09f1

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/backup/move-to-azure-monitor-alerts.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Switch to Azure Monitor based alerts for Azure Backup
33
description: This article describes the new and improved alerting capabilities via Azure Monitor and the process to configure Azure Monitor.
44
ms.topic: how-to
5-
ms.date: 09/14/2022
5+
ms.date: 03/31/2023
66
ms.service: backup
77
author: jyothisuri
88
ms.author: jsuri
@@ -48,6 +48,10 @@ The following table lists the differences between classic backup alerts and buil
4848
| **Notification suppression for database backup scenarios** | When there are multiple failures for the same database due to the same error code, a single alert is generated (with the occurrence count updated for each failure type) and a new alert is only generated when the original alert is inactivated. | The behavior is currently different. Here, a separate alert is generated for every backup failure. If there's a window of time when backups will fail for a certain known item (for example, during a maintenance window), you can create a suppression rule to suppress email noise for that backup item during the given period. |
4949
| **Pricing** | There are no additional charges for this solution. | Alerts for critical operations/failures generate by default (that you can view in the Azure portal or via non-portal interfaces) at no additional charge. However, to route these alerts to a notification channel (such as email), it incurs a minor charge for notifications beyond the *free tier* (of 1000 emails per month). Learn more about [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/). |
5050

51+
> [!NOTE]
52+
>- If you've existing custom Azure Resource Graph (ARG) queries written on classic alerts data, you'll need to update these queries to fetch information from Azure Monitor-based alerts. You can use the *AlertsManagementResources* table in ARG to query Azure Monitor alerts data.
53+
>- If you send classic alerts to Log Analytics workspace/Storage account/Event Hub via diagnostics settings, you'll also need to update these automation. To send the fired Azure Monitor based alerts to a destination of your choice, you can create an alert processing rule and action group that routes these alerts to a logic app, webhook, or runbook that in turn sends these alerts to the required destination.
54+
5155
Azure Backup now provides a guided experience via Backup center that allows you to switch to built-in Azure Monitor alerts and notifications with just a few selects. To perform this action, you need to have access to the *Backup Contributor* and *Monitoring Contributor* Azure role-based access control (Azure RBAC) roles to the subscription.
5256

5357
Follow these steps:

0 commit comments

Comments
 (0)