Skip to content

Commit 4ddd401

Browse files
Update alerts-log-webhook.md
1 parent e214b8f commit 4ddd401

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.subservice: alerts
1414
When a [log alert is created in Azure](alerts-log.md), you have the option of [configuring it by using action groups](action-groups.md) to perform one or more actions. This article describes the different webhook actions that are available and shows how to configure a custom JSON-based webhook.
1515

1616
> [!NOTE]
17-
> You also can use the [common alert schema](https://aka.ms/commonAlertSchemaDocs) for your webhook integrations. The common alert schema provides the advantage of having a single extensible and unified alert payload across all the alert services in Azure Monitor. [Learn about the common alert schema definitions.](https://aka.ms/commonAlertSchemaDefinitions)
17+
> You also can use the [common alert schema](https://aka.ms/commonAlertSchemaDocs) for your webhook integrations. The common alert schema provides the advantage of having a single extensible and unified alert payload across all the alert services in Azure Monitor.Please note that the common alert schema does not honour the custom JSON option for log alerts. It defers to the common alert schema payload if that is selected irrespective of the customization you might have done at the alert rule level. [Learn about the common alert schema definitions.](https://aka.ms/commonAlertSchemaDefinitions)
1818
1919
## Webhook actions
2020

0 commit comments

Comments
 (0)