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/azure-monitor/alerts/alerts-log.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ You can also [create log alert rules using Azure Resource Manager templates](../
61
61
62
62
|Field |Description |
63
63
|---------|---------|
64
-
|Dimension name|Dimensions can be either number or string columns. Dimensions are used to monitor specific time series and provide context to a fired alert.<br>Splitting on the Azure Resource ID column makes the specified resource into the alert target. If an Resource ID column is detected, it is selected automatically and changes the context of the fired alert to the record's resource. |
64
+
|Dimension name|Dimensions can be either number or string columns. Dimensions are used to monitor specific time series and provide context to a fired alert.<br>Splitting on the Azure Resource ID column makes the specified resource into the alert target. If a Resource ID column is detected, it is selected automatically and changes the context of the fired alert to the record's resource. |
65
65
|Operator|The operator used on the dimension name and value. |
66
66
|Dimension values|The dimension values are based on data from the last 48 hours. Select **Add custom value** to add custom dimension values. |
67
67
@@ -118,10 +118,11 @@ You can also [create log alert rules using Azure Resource Manager templates](../
118
118
> [!NOTE]
119
119
> This section above describes creating alert rules using the new alert rule wizard.
120
120
> The new alert rule experience is a little different than the old experience. Please note these changes:
121
-
> - Previously, search results were included in the payloads of the triggered alert and its associated notifications. This was a limited and error prone solution. To get detailed context information about the alert so that you can decide on the appropriate action :
122
-
> - The recommended best practice it to use [Dimensions](alerts-unified-log.md#split-by-alert-dimensions). Dimensions provide the column value that fired the alert, giving you context for why the alert fired and how to fix the issue.
123
-
> - When you need to investigate in the logs, use the link in the alert to the search results in Logs.
124
-
> - If you need the raw search results or for any other advanced customizations, use Logic Apps.
121
+
> - Previously, search results were included in the payloads of the triggered alert and its associated notifications. This was a limited solution, since the email included only 10 rows from the unfiltered results while the webhook payload contained 1000 unfiltered results.
122
+
> To get detailed context information about the alert so that you can decide on the appropriate action :
123
+
> - We recommend using [Dimensions](alerts-unified-log.md#split-by-alert-dimensions). Dimensions provide the column value that fired the alert, giving you context for why the alert fired and how to fix the issue.
124
+
> - When you need to investigate in the logs, use the link in the alert to the search results in Logs.
125
+
> - If you need the raw search results or for any other advanced customizations, use Logic Apps.
125
126
> - The new alert rule wizard does not support customization of the JSON payload.
126
127
> - Use custom properties in the [new API](/rest/api/monitor/scheduledqueryrule-2021-08-01/scheduled-query-rules/create-or-update#actions) to add static parameters and associated values to the webhook actions triggered by the alert.
127
128
> - For more advanced customizations, use Logic Apps.
0 commit comments