Schedule demo

Microsoft Azure Logic App (Consumption)


Microsoft Azure Logic App (Consumption) - An Overview

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.

Creating a new Microsoft Azure Logic App (Consumption) Monitor

To learn how to create a new Microsoft Azure Logic App (Consumption) Monitor, click here.

Monitored Parameters

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:

  • Availability tab gives the Availability history for the past 24 hours or 30 days.
  • Performance tab gives the Health Status and events for the past 24 hours or 30 days.
  • List view enables you to perform bulk admin configurations.

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:

Trigger Statistics

Parameter Description
TRIGGER LATENCY
Trigger LatencyThe average latency of the completed workflow triggers between the poll interval (in seconds).
Trigger Fire LatencyThe average latency of the workflow triggers fired between the poll interval (in seconds).
Trigger Success LatencyThe average latency of the successful workflow triggers between the poll interval (in seconds).
TRIGGERS FIRED
Triggers FiredThe total number of workflow triggers fired between the poll interval.
TRIGGERS STARTED
Triggers StartedThe total number of workflow triggers started between the poll interval.
TRIGGERS COMPLETED
Triggers CompletedThe total number of workflow triggers completed between the poll interval.
TRIGGERS SUCCEEDED
Triggers SucceededThe total number of workflow triggers succeeded between the poll interval.
TRIGGERS FAILED
Triggers FailedThe total number of workflow triggers failed between the poll interval.
TRIGGERS SKIPPED
Triggers SkippedThe total number of workflow triggers skipped between the poll interval.
TRIGGER THROTTLED EVENTS
Trigger Throttled EventsThe total number of workflow trigger throttled events that occurred between the poll interval.

Action Statistics

Parameter Description
ACTION LATENCY
Action LatencyThe average latency of the completed workflow actions between the poll interval (in seconds).
Action Success LatencyThe average latency of the successful workflow actions between the poll interval (in seconds).
ACTIONS STARTED
Actions StartedThe total number of workflow actions started between the poll interval.
ACTIONS COMPLETED
Actions CompletedThe total number of workflow actions completed between the poll interval.
ACTIONS SUCCEEDED
Actions SucceededThe total number of workflow actions that succeeded between the poll interval.
ACTIONS FAILED
Actions FailedThe total number of workflow actions that failed between the poll interval.
ACTIONS SKIPPED
Actions SkippedThe total number of workflow actions skipped between the poll interval.
ACTION THROTTLED EVENTS
Action Throttled EventsThe total number of workflow action throttled events that occurred between the poll interval.

Run Statistics

Parameter Description
RUN LATENCY
Run LatencyThe average latency of the completed workflow runs between the poll interval (in seconds).
Run Success LatencyThe average latency of the successful workflow runs between the poll interval (in seconds).
RUN FAILURE RATIO
Run Failure RatioThe average percentage of the failed workflow runs between the poll interval (in %).
RUNS STARTED
Runs StartedThe total number of workflow runs started between the poll interval.
RUNS COMPLETED
Runs CompletedThe total number of workflow runs completed between the poll interval.
RUNS SUCCEEDED
Runs SucceededThe total number of workflow runs that succeeded between the poll interval.
RUNS FAILED
Runs FailedThe total number of workflow runs that failed between the poll interval.
RUN THROTTLED EVENTS
Run Throttled EventsThe total number of workflow run throttled events that occurred between the poll interval.
Run Start Throttled EventsThe total number of workflow run start throttled events that occurred between the poll interval.
RUNS CANCELLED
Runs CancelledThe total number of workflow runs cancelled between the poll interval.

Billable Executions

Parameter Description
BILLABLE EXECUTIONS
Total Billable ExecutionsThe total number of workflow executions billed between the polling interval.
BILLABLE TRIGGER EXECUTIONS
Billable Trigger ExecutionsThe total number of workflow trigger executions billed between the polling interval.
BILLABLE ACTION EXECUTIONS
Billable Action ExecutionsThe total number of workflow action executions billed between the polling interval.
BILLABLE NATIVE OPERATION EXECUTIONS
Billable Native Operation ExecutionsThe total number of native operation executions billed between the polling interval.
BILLABLE STANDARD CONNECTOR EXECUTIONS
Billable Standard Connector ExecutionsThe total number of standard connector executions billed between the polling interval.
BILLABLE STORAGE CONSUMPTION EXECUTIONS
Billable Storage Consumption ExecutionsThe total number of storage consumption executions billed between the polling interval.

Workflow Failed History

ParameterDescription
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:
  • Maximum of 10 triggers (as per Azure's platform limits — Refer here) are fetched per workflow.
  • Recent 250 failed trigger history records are fetched per trigger.
Trigger IdentifierThe unique identifier of the trigger execution.
StatusThe execution status of the trigger.
Start TimeThe date and time when the trigger execution started.
End TimeThe date and time when the trigger execution ended.
Total Duration(sec)The duration of the trigger execution in seconds.
FiredThe indicator showing whether the trigger fired.
Trigger NameThe 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 IdentifierThe unique identifier of the workflow run.
StatusThe execution status of the workflow run.
Start TimeThe date and time when the workflow run started.
End TimeThe date and time when the workflow run ended.
Total Duration(sec)The duration of the workflow run.
Trigger NameThe name of the trigger that initiated the run.
 
Note:
  • The Workflow Failed History metrics are categorized under Performance Polling. Data collection for these attributes will be disabled by default. To modify the polling interval, go to Settings → Performance Polling. In the Optimize Data Collection tab, select Azure Logic App (Consumption) as the Monitor Type and Workflow Failed History as the Metric Name. Choose 'Configure a custom interval' and set the polling interval between the acceptable range (Min 1 hour to Max of 24 hours). Data collection will be stopped if the polling interval exceeds 24 hours or is set below 1 hour.
  • Click here to know more on Performance polling.

Configuration

ParameterDescription
CONFIGURATION
Resource Group NameThe name of the resource group.
LocationThe location of the resource.
Provisioning StateThe current provisioning state of the service. Possible values: refer here
StateThe state of the resource. Possible values:
  • Completed
  • Deleted
  • Disabled
  • Enabled
  • NotSpecified
  • Suspended
VersionThe version of the resource.
Access EndpointThe access endpoint of the resource.
Creation TimeThe timestamp of the resource creation.
Last Modified TimeThe timestamp of the last resource modification.

Loved by customers all over the world

"Standout Tool With Extensive Monitoring Capabilities"

It allows us to track crucial metrics such as response times, resource utilization, error rates, and transaction performance. The real-time monitoring alerts promptly notify us of any issues or anomalies, enabling us to take immediate action.

Reviewer Role: Research and Development

carlos-rivero
"I like Applications Manager because it helps us to detect issues present in our servers and SQL databases."
Carlos Rivero

Tech Support Manager, Lexmark

Trusted by over 6000+ businesses globally