Skip to content

Latest commit

 

History

History
149 lines (99 loc) · 8.86 KB

File metadata and controls

149 lines (99 loc) · 8.86 KB
title Monitor logic app workflows
description Start here to learn about monitoring workflows in Azure Logic Apps.
ms.service azure-logic-apps
ms.topic concept-article
ms.custom horz-monitor
ms.date 07/18/2025

Monitor workflows in Azure Logic Apps

[!INCLUDE horz-monitor-intro]

For a detailed guide describing how to check Azure Logic Apps workflow status, view workflow run history, and set up alerts, see Check workflow status, view workflow run history, and set up alerts.

[!INCLUDE horz-monitor-insights]

Application Insights

You can set up Application Insights for a logic app or Log Analytics workspace after creation.

Enable and view enhanced telemetry in Application Insights for Standard workflows in Azure Logic Apps 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.

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.

[!INCLUDE horz-monitor-resource-types] For more information about the resource types for Azure Logic Apps, see Azure Logic Apps monitoring data reference.

[!INCLUDE horz-monitor-data-storage]

[!INCLUDE horz-monitor-platform-metrics]

[!INCLUDE horz-monitor-resource-logs]

Monitoring for B2B workflows

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.

[!INCLUDE horz-monitor-activity-log]

[!INCLUDE horz-monitor-analyze-data]

[!INCLUDE horz-monitor-external-tools]

[!INCLUDE horz-monitor-kusto-queries]

For a detailed guide showing how to view and create queries for Azure Logic Apps, see View and create queries for monitoring and tracking.

Sample Kusto queries

Here are some sample queries for analyzing Azure Logic Apps workflow executions.

Total executions

Total billable executions by operation name.

AzureDiagnostics
| where ResourceProvider == "MICROSOFT.LOGIC"
| where Category == "WorkflowRuntime" 
| where OperationName has "workflowTriggerStarted" or OperationName has "workflowActionStarted" 
| summarize dcount(resource_runId_s) by OperationName, resource_workflowName_s

Execution distribution

Hourly time chart for logic app execution distribution by workflow.

AzureDiagnostics 
| where ResourceProvider == "MICROSOFT.LOGIC"
| where Category == "WorkflowRuntime"
| where OperationName has "workflowRunStarted"
| summarize dcount(resource_runId_s) by bin(TimeGenerated, 1h), resource_workflowName_s
| render timechart 

Execution status summary

Completed executions by workflow, status, and error.

AzureDiagnostics
| where ResourceProvider == "MICROSOFT.LOGIC"
| where OperationName has "workflowRunCompleted"
| summarize dcount(resource_runId_s) by resource_workflowName_s, status_s, error_code_s
| project LogicAppName = resource_workflowName_s , NumberOfExecutions = dcount_resource_runId_s , RunStatus = status_s , Error = error_code_s 

Triggered failures count

Action or trigger failures for all logic app workflow executions by resource name.

AzureDiagnostics
| where ResourceProvider  == "MICROSOFT.LOGIC"  
| where Category == "WorkflowRuntime" 
| where status_s == "Failed" 
| where OperationName has "workflowActionCompleted" or OperationName has "workflowTriggerCompleted" 
| extend ResourceName = coalesce(resource_actionName_s, resource_triggerName_s) 
| extend ResourceCategory = substring(OperationName, 34, strlen(OperationName) - 43) | summarize dcount(resource_runId_s) by code_s, ResourceName, resource_workflowName_s, ResourceCategory, _ResourceId
| project ResourceCategory, ResourceName , FailureCount = dcount_resource_runId_s , ErrorCode = code_s, LogicAppName = resource_workflowName_s, _ResourceId 
| order by FailureCount desc 

[!INCLUDE horz-monitor-alerts]

[!INCLUDE horz-monitor-insights-alerts]

Note

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.

Azure Logic Apps alert rules

The following table lists some alert rules for Azure Logic Apps. These alerts are just examples. You can set alerts for any metric, log entry, or activity log entry that's listed in the Azure Logic Apps monitoring data reference.

Alert type Condition Description
Metric Triggers Failed Whenever the count for Triggers Failed is greater than or equal to 1
Activity Log Workflow Deleted Whenever the Activity Log has an event with Category='Administrative', Signal name='Delete Workflow (Workflow)'

[!INCLUDE horz-monitor-advisor-recommendations]

Related content