Microsoft Azure Logic Apps is a cloud-based service that enables users to automate workflows and integrate various services and applications. There are two main types of Logic Apps: Consumption Logic Apps and Standard Logic Apps.
A Consumption logic app can have only one workflow that runs in a multitenant Azure Logic Apps environment or an integration service environment. In contrast, a Standard logic app can have one or multiple workflows that run in a single-tenant Azure Logic Apps environment or an App Service Environment v3 (ASE v3).
A capable Azure Logic Apps (Consumption) monitoring tool is essential to ensure that workflows run smoothly, efficiently, and as expected. Read on to learn how to achieve this with Applications Manager.
To learn how to create a new Microsoft Azure Logic App (Consumption) Monitor, click here.
Navigate to the Category View by clicking the Monitors tab. Hover over 'Child Monitors' under Microsoft Azure in the Cloud Apps table, and then select the Logic Apps (Consumption) monitor from the displayed tooltip. This action will display the bulk configuration view for Azure Logic App (Consumption) in three tabs:
The Microsoft Azure monitor provides a brief detail of the Azure Logic App (Consumption) under the given subscription. Following are the list of metrics monitored in Azure Logic App (Consumption) Monitoring in their corresponding tabs:
| Parameter | Description |
|---|---|
| TRIGGER LATENCY | |
| Trigger Latency | The average latency of the completed workflow triggers between the poll interval (in seconds). |
| Trigger Fire Latency | The average latency of the workflow triggers fired between the poll interval (in seconds). |
| Trigger Success Latency | The average latency of the successful workflow triggers between the poll interval (in seconds). |
| TRIGGERS FIRED | |
| Triggers Fired | The total number of workflow triggers fired between the poll interval. |
| TRIGGERS STARTED | |
| Triggers Started | The total number of workflow triggers started between the poll interval. |
| TRIGGERS COMPLETED | |
| Triggers Completed | The total number of workflow triggers completed between the poll interval. |
| TRIGGERS SUCCEEDED | |
| Triggers Succeeded | The total number of workflow triggers succeeded between the poll interval. |
| TRIGGERS FAILED | |
| Triggers Failed | The total number of workflow triggers failed between the poll interval. |
| TRIGGERS SKIPPED | |
| Triggers Skipped | The total number of workflow triggers skipped between the poll interval. |
| TRIGGER THROTTLED EVENTS | |
| Trigger Throttled Events | The total number of workflow trigger throttled events that occurred between the poll interval. |
| Parameter | Description |
|---|---|
| ACTION LATENCY | |
| Action Latency | The average latency of the completed workflow actions between the poll interval (in seconds). |
| Action Success Latency | The average latency of the successful workflow actions between the poll interval (in seconds). |
| ACTIONS STARTED | |
| Actions Started | The total number of workflow actions started between the poll interval. |
| ACTIONS COMPLETED | |
| Actions Completed | The total number of workflow actions completed between the poll interval. |
| ACTIONS SUCCEEDED | |
| Actions Succeeded | The total number of workflow actions that succeeded between the poll interval. |
| ACTIONS FAILED | |
| Actions Failed | The total number of workflow actions that failed between the poll interval. |
| ACTIONS SKIPPED | |
| Actions Skipped | The total number of workflow actions skipped between the poll interval. |
| ACTION THROTTLED EVENTS | |
| Action Throttled Events | The total number of workflow action throttled events that occurred between the poll interval. |
| Parameter | Description |
|---|---|
| RUN LATENCY | |
| Run Latency | The average latency of the completed workflow runs between the poll interval (in seconds). |
| Run Success Latency | The average latency of the successful workflow runs between the poll interval (in seconds). |
| RUN FAILURE RATIO | |
| Run Failure Ratio | The average percentage of the failed workflow runs between the poll interval (in %). |
| RUNS STARTED | |
| Runs Started | The total number of workflow runs started between the poll interval. |
| RUNS COMPLETED | |
| Runs Completed | The total number of workflow runs completed between the poll interval. |
| RUNS SUCCEEDED | |
| Runs Succeeded | The total number of workflow runs that succeeded between the poll interval. |
| RUNS FAILED | |
| Runs Failed | The total number of workflow runs that failed between the poll interval. |
| RUN THROTTLED EVENTS | |
| Run Throttled Events | The total number of workflow run throttled events that occurred between the poll interval. |
| Run Start Throttled Events | The total number of workflow run start throttled events that occurred between the poll interval. |
| RUNS CANCELLED | |
| Runs Cancelled | The total number of workflow runs cancelled between the poll interval. |
| Parameter | Description |
|---|---|
| BILLABLE EXECUTIONS | |
| Total Billable Executions | The total number of workflow executions billed between the polling interval. |
| BILLABLE TRIGGER EXECUTIONS | |
| Billable Trigger Executions | The total number of workflow trigger executions billed between the polling interval. |
| BILLABLE ACTION EXECUTIONS | |
| Billable Action Executions | The total number of workflow action executions billed between the polling interval. |
| BILLABLE NATIVE OPERATION EXECUTIONS | |
| Billable Native Operation Executions | The total number of native operation executions billed between the polling interval. |
| BILLABLE STANDARD CONNECTOR EXECUTIONS | |
| Billable Standard Connector Executions | The total number of standard connector executions billed between the polling interval. |
| BILLABLE STORAGE CONSUMPTION EXECUTIONS | |
| Billable Storage Consumption Executions | The total number of storage consumption executions billed between the polling interval. |
| Parameter | Description |
|---|---|
| FAILED TRIGGER HISTORY: This table shows failed trigger events for enabled workflows, filtering based on the notes below, helping you quickly identify and resolve issues.
Note:
|
|
| Trigger Identifier | The unique identifier of the trigger execution. |
| Status | The execution status of the trigger. |
| Start Time | The date and time when the trigger execution started. |
| End Time | The date and time when the trigger execution ended. |
| Total Duration(sec) | The duration of the trigger execution in seconds. |
| Fired | The indicator showing whether the trigger fired. |
| Trigger Name | The name of the trigger. |
| FAILED RUN HISTORY: This table shows failed run events for enabled workflows, filtering based on the notes below, helping you quickly identify execution failures and take corrective actions.
Note: Recent 250 failed run history records are fetched across all workflows.
|
|
| Run Identifier | The unique identifier of the workflow run. |
| Status | The execution status of the workflow run. |
| Start Time | The date and time when the workflow run started. |
| End Time | The date and time when the workflow run ended. |
| Total Duration(sec) | The duration of the workflow run. |
| Trigger Name | The name of the trigger that initiated the run. |
| Parameter | Description |
|---|---|
| CONFIGURATION | |
| Resource Group Name | The name of the resource group. |
| Location | The location of the resource. |
| Provisioning State | The current provisioning state of the service. Possible values: refer here |
| State | The state of the resource. Possible values:
|
| Version | The version of the resource. |
| Access Endpoint | The access endpoint of the resource. |
| Creation Time | The timestamp of the resource creation. |
| Last Modified Time | The timestamp of the last resource modification. |
Thank you for your feedback!
