Skip to content

Commit b7df160

Browse files
committed
made changes based on Yaniv's comments
1 parent cf034de commit b7df160

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/azure-monitor/alerts/alerts-log.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -25,16 +25,16 @@ You can also [create log alert rules using Azure Resource Manager templates](../
2525
> [!NOTE]
2626
> This article describes creating alert rules using the new alert rule wizard.
2727
> The new alert rule experience is a little different than the old experience. Please note these changes:
28-
> - 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 information about the alert:
29-
> - Use [dimensions](alerts-unified-log.md#split-by-alert-dimensions). Dimensions provide the column value that fired the alert.
30-
> - Use the link in the alert to the search results in Logs.
31-
> - Customize your experience using Logic Apps if you need the raw search results..
32-
> - The new alert rule wizard does not support customization of the email or the JSON payload.
28+
> - 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 :
29+
> -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.
30+
> - When you need to investigate in the logs, use the link in the alert to the search results in Logs.
31+
> -If you need the raw search results or for any other advanced customizations, use Logic Apps.
32+
> - The new alert rule wizard does not support customization of the JSON payload.
3333
> - Use custom properties in the [new API](/rest/api/monitor/scheduledqueryrule-2021-08-01/scheduled-query-rules/create-or-update#actions) to add static key:value pairs to the webhook that is sent out.
34-
> - For more advanced customizations, use Logic Apps to align Log Alerts with other alert types.
34+
> - For more advanced customizations, use Logic Apps.
3535
> - The new alert rule wizard does not support customization of the email subject.
36-
> - In most cases, customers use the custom email subject to indicate the resource on which the alert fired. Use the [new API](alerts-unified-log.md#split-by-alert-dimensions) to get the resource id.
37-
> - For more advanced customizations, use Logic Apps to align Log Alerts with other alert types.
36+
> - Customers often use the custom email subject to indicate the resource on which the alert fired, instead of using the Log Analytics workspace. Use the [new API](alerts-unified-log.md#split-by-alert-dimensions) to trigger an alert of the desired resource using the resource id column.
37+
> - For more advanced customizations, use Logic Apps.
3838
3939

4040
1. In the [portal](https://portal.azure.com/), select the relevant resource.

0 commit comments

Comments
 (0)