Skip to content

Commit 9eb5c79

Browse files
authored
Update alerts-create-log-alert-rule.md
findings from this IcM https://portal.microsofticm.com/imp/v3/incidents/incident/448235514/summary
1 parent 24eeccc commit 9eb5c79

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-monitor/alerts/alerts-create-log-alert-rule.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ description: This article shows you how to create a new log search alert rule.
44
author: AbbyMSFT
55
ms.author: abbyweisberg
66
ms.topic: how-to
7-
ms.date: 11/27/2023
8-
ms.reviewer: harelbr
7+
ms.date: 02/22/2024
8+
ms.reviewer: nolavime
99
---
1010

1111
# Create or edit a log search alert rule
@@ -84,7 +84,7 @@ Alerts triggered by these alert rules contain a payload that uses the [common al
8484
Select values for these fields:
8585
8686
- **Resource ID column**: In general, if your alert rule scope is a workspace, the alerts are fired on the workspace. If you want a separate alert for each affected Azure resource, you can:
87-
- use the ARM **Azure Resource ID** column as a dimension
87+
- use the ARM **Azure Resource ID** column as a dimension (notice that by using this option the alert will be fired on the **workspace** with the **Azure Resource ID** column as a dimension.
8888
- specify it as a dimension in the Azure Resource ID property, which makes the resource returned by your query the target of the alert, so alerts are fired on the resource returned by your query, such as a virtual machine or a storage account, as opposed to in the workspace. When you use this option, if the workspace gets data from resources in more than one subscription, alerts can be triggered on resources from a subscription that is different from the alert rule subscription.
8989
9090
|Field |Description |

0 commit comments

Comments
 (0)