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-overview.md
+18-8Lines changed: 18 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Start here to learn about monitoring workflows in Azure Logic Apps.
4
4
ms.service: azure-logic-apps
5
5
ms.topic: conceptual
6
6
ms.custom: horz-monitor
7
-
ms.date: 07/11/2024
7
+
ms.date: 03/07/2025
8
8
---
9
9
10
10
# Monitor workflows in Azure Logic Apps
@@ -17,11 +17,11 @@ For a detailed guide describing how to check Azure Logic Apps workflow status, v
17
17
18
18
### Application Insights
19
19
20
-
You can set up Application Insights for a workspace or for a logic app after creation.
20
+
You can set up Application Insights for a logic app or Log Analytics workspace after creation.
21
21
22
-
[Enable and view enhanced telemetry in Application Insights for Standard workflows in Azure Logic Apps](enable-enhanced-telemetry-standard-workflows.md) shows how to turn on enhanced telemetry collection for a Standard logic app in Application Insights and view the collected data after the workflow finishes a run.
22
+
[Enable and view enhanced telemetry in Application Insights for Standard workflows in Azure Logic Apps](enable-enhanced-telemetry-standard-workflows.md) shows how to turn on enhanced telemetry collection for a Standard logic app resource in Application Insights and view the collected data after the workflow finishes a run.
23
23
24
-
If your logic app's creation and deployment settings support using Application Insights, you can optionally enable diagnostics logging and tracing for your logic app's workflow. For more information, see [Enable or open Application Insights after deployment](create-single-tenant-workflows-azure-portal.md#enable-open-application-insights).
24
+
If your logic app creation and deployment settings support using Application Insights, you can optionally enable diagnostics logging and tracing for your logic app workflow. For more information, see [Enable or open Application Insights after deployment](create-single-tenant-workflows-azure-portal.md#enable-open-application-insights).
For more information about the resource types for Azure Logic Apps, see [Azure Logic Apps monitoring data reference](monitor-logic-apps-reference.md).
@@ -39,14 +39,20 @@ For more information about the resource types for Azure Logic Apps, see [Azure L
39
39
40
40
- To learn how to set up diagnostic logging and monitor logic apps in Microsoft Defender for Cloud, see [Set up logging to monitor logic apps in Microsoft Defender for Cloud](healthy-unhealthy-resource.md).
41
41
42
-
- For the available resource log categories, their associated Log Analytics tables, and the log's schemas for Azure Logic Apps, see [Azure Logic Apps monitoring data reference](monitor-logic-apps-reference.md#resource-logs).
42
+
- For the available resource log categories, their associated Log Analytics tables, and log schemas for Azure Logic Apps, see [Azure Logic Apps monitoring data reference](monitor-logic-apps-reference.md#resource-logs).
43
43
44
44
## Monitoring for B2B workflows
45
45
46
46
Azure Logic Apps includes built-in tracking that you can enable for parts of your workflow. To help you monitor the successful delivery or receipt, errors, and properties for business-to-business (B2B) messages, you can create and use AS2, X12, and custom tracking schemas in your integration account.
47
47
48
-
- To monitor an automated business-to-business (B2B) messaging workflow in Azure Logic Apps, see [Set up Azure Monitor logs and collect diagnostics data for B2B messages](monitor-b2b-messages-log-analytics.md).
49
-
- For a reference guide to the syntax and attributes for the tracking schemas, see [Tracking schemas for monitoring B2B messages](tracking-schemas-as2-x12-custom.md).
48
+
- To monitor a Consumption workflow that handles business-to-business (B2B) messages in Azure Logic Apps, see [Monitor and track B2B messages in Consumption workflows with Azure Monitor and Azure Logic Apps](monitor-track-b2b-messages-consumption.md).
49
+
50
+
- To monitor a Standard workflow that handles business-to-business (B2B) messages in Azure Logic Apps, see [Monitor and track B2B transactions in Standard workflows](monitor-track-b2b-transactions-standard.md).
51
+
52
+
- For a reference guide to the syntax and attributes for the tracking schemas, see the following documentation:
53
+
54
+
-[Tracking schemas for B2B messages in Consumption workflows](tracking-schemas-consumption.md)
55
+
-[Tracking schemas for B2B transactions in Standard workflows](tracking-schemas-standard.md)
> Available alert signals differ between Consumption and Standard logic apps. For example, Consumption logic apps have many trigger-related signals, such as **Triggers Completed** and **Triggers Failed**, while Standard workflows have the **Workflow Triggers Completed Count** and **Workflow Triggers Failure Rate** signals.
129
+
>
130
+
> Available alert signals differ between Consumption and Standard logic apps. For example,
131
+
> Consumption logic apps have many trigger-related signals, such as **Triggers Completed**
132
+
> and **Triggers Failed**, while Standard workflows have the **Workflow Triggers Completed Count**
-[AzureDiagnostics](/azure/azure-monitor/reference/tables/AzureDiagnostics#columns). Logs are collected in the **AzureDiagnostics** table under the resource provider name of `MICROSOFT.LOGIC`.
- For an overview of monitoring Azure Logic Apps, see [Monitor Azure Logic Apps](monitor-logic-apps-overview.md).
67
-
- For a description of monitoring workflow status and history and creating alerts, see [Monitor workflows](monitor-logic-apps.md).
71
+
- For an overview about monitoring Azure Logic Apps, see [Monitor Azure Logic Apps](monitor-logic-apps-overview.md).
72
+
- For a description about monitoring workflow status and history and creating alerts, see [Monitor workflows](monitor-logic-apps.md).
68
73
- For details about monitoring Azure resources, see [Monitor Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource).
Copy file name to clipboardExpand all lines: articles/logic-apps/monitor-track-b2b-messages-consumption.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,22 @@
1
1
---
2
-
title: Monitor B2B messages with Azure Monitor
3
-
description: Troubleshoot AS2, X12, and EDIFACT messages with Azure Monitor logs and collecting diagnostics data for Azure Logic Apps.
2
+
title: Monitor and track B2B messages - Consumption workflows
3
+
description: Monitor, track, and troubleshoot AS2, X12, and EDIFACT messages with Azure Monitor by collecting diagnostics data for Consumption workflows in Azure Logic Apps.
4
4
services: logic-apps
5
5
ms.suite: integration
6
6
ms.reviewer: divswa, azla
7
7
ms.topic: how-to
8
-
ms.date: 01/04/2024
8
+
ms.date: 02/28/2025
9
9
---
10
10
11
-
# Set up Azure Monitor logs and collect diagnostics data for B2B messages in Azure Logic Apps
11
+
# Monitor and track B2B messages in Consumption workflows with Azure Monitor and Azure Logic Apps
> This article applies only to Consumption logic apps. For information about monitoring Standard logic apps, review
17
-
> [Enable or open Application Insights after deployment for Standard logic apps](create-single-tenant-workflows-azure-portal.md#enable-open-application-insights).
16
+
> This article applies only to Consumption logic app workflows. For Standard logic app workflows, see the following documentation:
17
+
>
18
+
> -[Enable or open Application Insights after deployment for Standard workflows](create-single-tenant-workflows-azure-portal.md#enable-open-application-insights)
19
+
> -[Monitor and track B2B transactions in Standard workflows](monitor-track-b2b-transactions-standard.md)
18
20
19
21
After you set up B2B communication between trading partners in your integration account, those partners can exchange messages by using protocols such as AS2, X12, and EDIFACT. To check that this communication works the way you expect, you can set up [Azure Monitor logs](/azure/azure-monitor/logs/data-platform-logs) for your integration account. [Azure Monitor](/azure/azure-monitor/overview) helps you monitor your cloud and on-premises environments so that you can more easily maintain their availability and performance. By using Azure Monitor logs, you can record and store data about runtime data and events, such as trigger events, run events, and action events in a [Log Analytics workspace](/azure/azure-monitor/essentials/resource-logs#send-to-log-analytics-workspace). For messages, logging also collects information such as:
0 commit comments