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/platform/alerts-common-schema-integrations.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: How to integrate the common alert schema with Logic Apps
3
3
description: Learn how to create a logic app that leverages the common alert schema to handle all your alerts.
4
-
author: anantr
4
+
author: ananthradhakrishnan
5
5
services: azure-monitor
6
6
ms.service: azure-monitor
7
7
ms.topic: conceptual
@@ -15,10 +15,10 @@ This article shows you how to create a logic app that leverages the common alert
15
15
16
16
## Overview
17
17
18
-
The [common alert schema](https://aka.ms/commonAlertSchemaDocs) provides a standardised and extensible JSON schema across all your different alert types. The common alert schema is most useful when leveraged programmatically – through webhooks, runbooks, and logic apps. In this article, we demonstrate how a single logic app can be authored to handle all your alerts. The same principles can be applied to other programmatic methods. The logic app described in this article creates well-defined variables for the ['essential' fields](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-common-schema-definitions#essentials-fields), and also describes how you can handle [alert type]('https://docs.microsoft.com/azure/azure-monitor/platform/alerts-common-schema-definitions#alert-context-fields') specific logic.
18
+
The [common alert schema](https://aka.ms/commonAlertSchemaDocs) provides a standardized and extensible JSON schema across all your different alert types. The common alert schema is most useful when leveraged programmatically – through webhooks, runbooks, and logic apps. In this article, we demonstrate how a single logic app can be authored to handle all your alerts. The same principles can be applied to other programmatic methods. The logic app described in this article creates well-defined variables for the ['essential' fields](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-common-schema-definitions#essentials-fields), and also describes how you can handle [alert type]('https://docs.microsoft.com/azure/azure-monitor/platform/alerts-common-schema-definitions#alert-context-fields') specific logic.
19
19
20
20
21
-
## Pre-requisites
21
+
## Prerequisites
22
22
23
23
This article assumes that the reader is familiar with
24
24
* Setting up alert rules ([metric](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-metric), [log](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-log), [activity log](https://docs.microsoft.com/azure/azure-monitor/platform/alerts-activity-log))
@@ -27,7 +27,7 @@ This article assumes that the reader is familiar with
27
27
28
28
## Create a logic app leveraging the common alert schema
29
29
30
-
1. Follow the steps outlined [here](https://docs.microsoft.com/azure/azure-monitor/platform/action-groups-logic-app) to create your logic app.
30
+
1. Follow the [steps outlined to create your logic app](https://docs.microsoft.com/azure/azure-monitor/platform/action-groups-logic-app).
31
31
32
32
1. Select the trigger: **When a HTTP request is received**.
33
33
@@ -128,7 +128,7 @@ This article assumes that the reader is familiar with
You can learn more about writing logic app expressions [here](https://docs.microsoft.com/azure/logic-apps/workflow-definition-language-functions-reference#logical-comparison-functions).
131
+
Learn more about [writing logic app expressions](https://docs.microsoft.com/azure/logic-apps/workflow-definition-language-functions-reference#logical-comparison-functions).
0 commit comments