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/logic-apps/monitor-logic-apps.md
+27-40Lines changed: 27 additions & 40 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,12 +49,8 @@ Each workflow run starts with a trigger, which either fires on a schedule or wai
49
49
50
50
To find your logic app, in the portal search box, enter **logic apps**, and then select **Logic apps**.
51
51
52
-

53
-
54
52
The Azure portal shows all the logic app resources in your Azure subscription. You can filter this list based on name, subscription, resource group, location, and so on.
55
53
56
-

57
-
58
54
1. Select your logic app resource. On your logic app menu, select **Overview**. On the **Overview** pane, select **Trigger history**.
59
55
60
56

@@ -92,12 +88,8 @@ Each workflow run starts with a trigger, which either fires on a schedule or wai
92
88
93
89
To find your logic app, in the portal search box, enter **logic apps**, and then select **Logic apps**.
94
90
95
-

96
-
97
91
The Azure portal shows all the logic app resources in your Azure subscription. You can filter this list based on name, subscription, resource group, location, and so on.
98
92
99
-

100
-
101
93
1. Select your logic app resource. On your logic app menu, select **Overview**. On the **Overview** pane, select **Trigger history**.
102
94
103
95

@@ -151,12 +143,8 @@ Each time a trigger successfully fires, Azure Logic Apps creates a workflow inst
151
143
152
144
To find your logic app, in the Azure search box, enter **logic apps**, and then select **Logic apps**.
153
145
154
-

155
-
156
146
The Azure portal shows all the logic apps in your Azure subscriptions. You can filter this list based on name, subscription, resource group, location, and so on.
157
147
158
-

159
-
160
148
1. Select your logic app resource. On your logic app menu, select **Overview**. On the **Overview** pane, select **Runs history**.
161
149
162
150
Under **Runs history**, all the past, current, and any waiting runs appear. If the trigger fires for multiple events or items at the same time, an entry appears for each item with the same date and time.
@@ -224,12 +212,8 @@ Each time a trigger successfully fires, Azure Logic Apps creates a workflow inst
224
212
225
213
To find your logic app, in the Azure search box, enter **logic apps**, and then select **Logic apps**.
226
214
227
-

228
-
229
215
The Azure portal shows all the logic apps in your Azure subscriptions. You can filter this list based on name, subscription, resource group, location, and so on.
230
216
231
-

232
-
233
217
1. Select your logic app resource. On your logic app menu, under **Workflows**, select **Workflows**, and then select your workflow.
234
218
235
219
> [!NOTE]
@@ -290,50 +274,53 @@ Each time a trigger successfully fires, Azure Logic Apps creates a workflow inst
290
274
291
275
## Set up monitoring alerts
292
276
293
-
To get alerts based on specific metrics or exceeded thresholds for your logic app, set up [alerts in Azure Monitor](../azure-monitor/alerts/alerts-overview.md). For more information, review [Metrics in Azure](../azure-monitor/data-platform.md). To set up alerts without using [Azure Monitor](../azure-monitor/logs/log-query-overview.md), follow these steps.
294
-
295
-
1. On your logic app menu, under **Monitoring**, select **Alerts**. On the toolbar, select **Create** > **Alert rule**.
277
+
To get alerts based on specific metrics or exceeded thresholds for your logic app, set up [alerts in Azure Monitor](../azure-monitor/alerts/alerts-overview.md). For more information, review [Metrics in Azure](../azure-monitor/data-platform.md).
296
278
297
-

279
+
To set up alerts without using [Azure Monitor](../azure-monitor/logs/log-query-overview.md), follow these steps, which apply to both Consumption and Standard logic app resources:
298
280
299
-
1. On the **Select a signal** pane, under **Signal type**, select the signal for which you want to get an alert.
281
+
1. On your logic app menu, under **Monitoring**, select **Alerts**. On the toolbar, select **Create** > **Alert rule**.
300
282
301
-
> [!TIP]
302
-
>
303
-
> You can use the search box, or to sort the signals alphabetically,
304
-
> select the **Signal name** column header.
283
+
1. On the **Create an alert rule** page, from the **Signal name** list, select the signal for which you want to get an alert.
305
284
306
285
For example, to send an alert when a trigger fails, follow these steps:
307
286
308
-
1.In the **Signal name**column, find and select the **Triggers Failed** signal.
287
+
1.From the **Signal name**list, select the **Triggers Failed** signal.
309
288
310
-

311
-
312
-
1. On the **Configure signal logic** pane, under **Alert logic**, set up your condition, and select **Done**, for example:
289
+
1. Under **Alert logic**, set up your condition, for example:
313
290
314
291
| Property | Example value |
315
292
|----------|---------------|
316
-
|**Operator**|**Greater than or equal to**|
293
+
|**Threshold**|**Static**|
317
294
|**Aggregation type**|**Count**|
318
-
|**Threshold value**|**1**|
295
+
|**Operator**|**Greater than or equal to**|
319
296
|**Unit**|**Count**|
320
-
|**Condition preview**|**Whenever the count of triggers failed is greater than or equal to 1**|
The **Preview** section now shows the condition that you set up, for example:
324
300
325
-
For more information, review [Create, view, and manage log alerts by using Azure Monitor](../azure-monitor/alerts/alerts-activity-log.md).
301
+
**Whenever the count Triggers Failed is greater than or equal to 1**
326
302
327
-
The following screenshot shows the finished condition:
303
+
1. Under **When to evaluate**, set up the schedule for checking the condition:
328
304
329
-

305
+
| Property | Example value |
306
+
|----------|---------------|
307
+
|**Check every**|**1 minute**|
308
+
|**Lookback period**|**5 minutes**|
309
+
310
+
For example, the finished condition looks similar to the following example, and the **Create an alert rule** page now shows the cost for running that alert:
330
311
331
-
The **Create an alert rule** page now shows the condition that you created and the cost for running that alert.
312
+

332
313
333
-

314
+
1. When you're done, select **Review + Create**.
315
+
316
+

317
+
318
+
and then select **Review + Create**,
334
319
335
320
1. If you're satisfied, select **Next: Details** to finish creating the rule.
336
321
322
+
For general information, see [Create an alert rule from a specific resource - Azure Monitor](../azure-monitor/alerts/alerts-create-new-alert-rule.md#create-or-edit-an-alert-rule-in-the-azure-portal).
323
+
337
324
## Next steps
338
325
339
326
*[Monitor logic apps with Azure Monitor](monitor-workflows-collect-diagnostic-data.md)
0 commit comments