Skip to content

Commit 8b3390d

Browse files
author
ecfan
committed
Draft updates
1 parent 6550dc6 commit 8b3390d

File tree

7 files changed

+27
-40
lines changed

7 files changed

+27
-40
lines changed
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
6.77 KB
Loading

articles/logic-apps/monitor-logic-apps.md

Lines changed: 27 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -49,12 +49,8 @@ Each workflow run starts with a trigger, which either fires on a schedule or wai
4949

5050
To find your logic app, in the portal search box, enter **logic apps**, and then select **Logic apps**.
5151

52-
![Screenshot shows the Azure portal search box and the search word logic apps, and selected option for Logic apps.](./media/monitor-logic-apps/find-your-logic-app.png)
53-
5452
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.
5553

56-
![Screenshot shows the Azure portal with all logic app resources in the selected Azure subscriptions.](./media/monitor-logic-apps/logic-apps-list-in-subscription.png)
57-
5854
1. Select your logic app resource. On your logic app menu, select **Overview**. On the **Overview** pane, select **Trigger history**.
5955

6056
![Screenshot shows Overview pane for Consumption logic app workflow with selected option named Trigger history.](./media/monitor-logic-apps/overview-logic-app-trigger-history-consumption.png)
@@ -92,12 +88,8 @@ Each workflow run starts with a trigger, which either fires on a schedule or wai
9288

9389
To find your logic app, in the portal search box, enter **logic apps**, and then select **Logic apps**.
9490

95-
![Screenshot shows Azure portal search box and the search word logic apps, and selected option for Logic apps.](./media/monitor-logic-apps/find-your-logic-app.png)
96-
9791
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.
9892

99-
![Screenshot shows Azure portal with all logic app resources in the selected Azure subscriptions.](./media/monitor-logic-apps/logic-apps-list-in-subscription.png)
100-
10193
1. Select your logic app resource. On your logic app menu, select **Overview**. On the **Overview** pane, select **Trigger history**.
10294

10395
![Screenshot shows Overview pane for Standard logic app with selected option named Trigger history.](./media/monitor-logic-apps/overview-logic-app-trigger-history-standard.png)
@@ -151,12 +143,8 @@ Each time a trigger successfully fires, Azure Logic Apps creates a workflow inst
151143

152144
To find your logic app, in the Azure search box, enter **logic apps**, and then select **Logic apps**.
153145

154-
![Screenshot shows Azure portal search box, with the search word logic apps, and selected option for Logic apps.](./media/monitor-logic-apps/find-your-logic-app.png)
155-
156146
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.
157147

158-
![Screenshot shows all logic apps in selected Azure subscriptions.](./media/monitor-logic-apps/logic-apps-list-in-subscription.png)
159-
160148
1. Select your logic app resource. On your logic app menu, select **Overview**. On the **Overview** pane, select **Runs history**.
161149

162150
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
224212

225213
To find your logic app, in the Azure search box, enter **logic apps**, and then select **Logic apps**.
226214

227-
![Screenshot shows Azure portal search box with the word logic apps, and selected option named Logic apps.](./media/monitor-logic-apps/find-your-logic-app.png)
228-
229215
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.
230216

231-
![Screenshot shows all logic apps in selected Azure subscriptions.](./media/monitor-logic-apps/logic-apps-list-in-subscription.png)
232-
233217
1. Select your logic app resource. On your logic app menu, under **Workflows**, select **Workflows**, and then select your workflow.
234218

235219
> [!NOTE]
@@ -290,50 +274,53 @@ Each time a trigger successfully fires, Azure Logic Apps creates a workflow inst
290274

291275
## Set up monitoring alerts
292276

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).
296278

297-
![Screenshot showing Azure portal, logic app menu with "Alerts" selected, and toolbar with "Create", "Alert rule" selected.](./media/monitor-logic-apps/add-new-alert-rule.png)
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:
298280

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**.
300282

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.
305284

306285
For example, to send an alert when a trigger fails, follow these steps:
307286

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.
309288

310-
![Screenshot showing "Select a signal pane", the "Signal name" column, and "Triggers Failed" signal selected.](./media/monitor-logic-apps/find-and-select-signal.png)
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:
313290

314291
| Property | Example value |
315292
|----------|---------------|
316-
| **Operator** | **Greater than or equal to** |
293+
| **Threshold** | **Static** |
317294
| **Aggregation type** | **Count** |
318-
| **Threshold value** | **1** |
295+
| **Operator** | **Greater than or equal to** |
319296
| **Unit** | **Count** |
320-
| **Condition preview** | **Whenever the count of triggers failed is greater than or equal to 1** |
321-
| **Aggregation granularity (Period)** | **1 minute** |
322-
| **Frequency of evaluation** | **Every 1 Minute** |
323-
|||
297+
| **Threshold value** | **1** |
298+
299+
The **Preview** section now shows the condition that you set up, for example:
324300

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**
326302

327-
The following screenshot shows the finished condition:
303+
1. Under **When to evaluate**, set up the schedule for checking the condition:
328304

329-
![Screenshot showing the condition for alert.](./media/monitor-logic-apps/set-up-condition-for-alert.png)
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:
330311

331-
The **Create an alert rule** page now shows the condition that you created and the cost for running that alert.
312+
![Screenshot shows the alert rule condition.](./media/monitor-logic-apps/set-up-condition-for-alert.png)
332313

333-
![Screenshot showing the new alert on the "Create an alert rule" page.](./media/monitor-logic-apps/finished-alert-condition-cost.png)
314+
1. When you're done, select **Review + Create**.
315+
316+
![Screenshot shows new alert on the page named Create an alert rule.](./media/monitor-logic-apps/finished-alert-condition-cost.png)
317+
318+
and then select **Review + Create**,
334319

335320
1. If you're satisfied, select **Next: Details** to finish creating the rule.
336321

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+
337324
## Next steps
338325

339326
* [Monitor logic apps with Azure Monitor](monitor-workflows-collect-diagnostic-data.md)

0 commit comments

Comments
 (0)