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
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-monitoring-use-azuremonitor.md
+23-3Lines changed: 23 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,11 +24,11 @@ In Azure Monitor, you can create your own alerts in a Log Analytics workspace. I
24
24
> [!IMPORTANT]
25
25
> For information on the cost of creating this query, see [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).
26
26
27
-
Select any of the graphs to open the **Logs** section of the Log Analytics workspace. In the **Logs** section, edit the queries and create alerts on them.
27
+
Open the **Logs** section of the Log Analytics workspace and write a query your own Logs. When you select **New Alert Rule**, the Azure Monitor alert-creation page opens, as shown in the following image.
28
28
29
-

29
+

30
30
31
-
When you select **New Alert Rule**, the Azure Monitor alert-creation page opens, as shown in the following image. Here the resource is already marked as the Log Analytics workspace, and action group integration is provided.
31
+
Here the resource is already marked as the Log Analytics workspace, and action group integration is provided.
The diagnostic data from the vault is pumped to the Log Analytics workspace with some lag. Every event arrives at the Log Analytics workspace *20 to 30 minutes* after it's pushed from the Recovery Services vault. Here are further details about the lag:
0 commit comments