Configure Workflow Monitoring for Azure Logic Apps
This page covers the Workflows tab of a Subscription configuration in the Nodinite Azure Logic Apps Logging and Monitoring Agent. It decides which workflows the agent monitors and which thresholds raise a Warning or Error on their Resources in your Monitor Views. Evaluating failed runs also requires the diagnostics Event Hub; see Configure Event Hubs. The other tabs are on the Subscription configuration page.
Understanding workflow thresholds
Besides failed runs, the agent can detect problems that don't fail: a workflow that stops running, runs far more often than expected, loops too many times, or runs too long. These are Non-Events checks, the same idea as Non-Events Monitoring, evaluated over a lookback period:
| Check | Detects | Example |
|---|---|---|
| Min execution count | Too few runs | A nightly import that didn't start |
| Max execution count | Too many runs | A trigger stuck in a retry storm |
| Max Action invocation count | Too many Actions in a single run | A loop processing far more items than normal |
| Duration | Runs that take too long | A slow backend holding up a workflow |
The agent evaluates every workflow that the exclusion filter doesn't remove, against its specific thresholds when it has them and the global thresholds otherwise. The Monitoring Service picks up the resulting state, so Alarm Plugins can notify the right people:
in enabled Resource Groups"] --> EX["fa:fa-filter Workflow exclusion filter"] EX -.->|"Name matches"| SKIP["fa:fa-ban Not monitored"] EX -->|"Included"| TH["fa:fa-sliders Specific thresholds
or Global thresholds"] TH --> ST["fa:fa-heart-pulse Resource state
OK, Warning, or Error"] ST --> MV["fa:fa-display Monitor Views
and Alarm Plugins"] style WF fill:#2678BD style EX fill:#E47528 style TH fill:#3F827B style MV fill:#9E59BB
Diagram: Workflows (blue) pass the exclusion filter (orange), the agent compares them with the thresholds (teal), and the resulting state reaches Monitor Views and Alarm Plugins (purple).
Global thresholds vs Specific thresholds
| Level | Where you set it | Applies to | When to use it |
|---|---|---|---|
| Global thresholds | Global thresholds tab | Every monitored workflow without its own entry | ✅ Recommended starting point |
| Specific thresholds | Specific thresholds tab, one entry per workflow | Only the named workflow | Workflows with a different schedule or volume |
You can also edit the thresholds of a single Logic App directly from its Resource; see Edit thresholds.
Workflows tab
The Workflows tab has three tabs:
The Workflows tab with its General, Global thresholds, and Specific thresholds tabs.
General Tab (Workflows)
- Enable monitoring of Workflows - When checked, the agent monitors the Workflows in the enabled Resource Groups
- Enable trigger evaluation of Workflows - When checked, the agent monitors the triggers of the enabled workflows
- Workflow exclusion filter - The list of RegEx expressions in use to exclude Azure Workflows from Monitoring
Workflow exclusion filter
You can exclude Workflows based on the name using a regular expression. Click the Add button to add a new entry.
Example of a RegEx entry that excludes Workflows by name.
Global Thresholds (Workflows)
You can configure Non-Events type Monitoring. This option is easier to use on the Logic App Resource; see Monitoring Logic Apps.
The Global thresholds tab sets the Warning and Error limits for every monitored workflow.
- Lookback time period - The time period to look back for Azure Workflow execution KPIs
- ⚠️ Min execution count - Warning - Warning threshold for the minimum number of executions in period (set value -1 to disable this check)
- ❌ Min execution count - Error - Error threshold for the minimum number of executions in period (set value -1 to disable this check)
- ⚠️ Max execution count - Warning - Warning threshold for the maximum number of executions in period (set value -1 to disable this check)
- ❌ Max execution count - Error - Error threshold for the maximum number of executions in period (set value -1 to disable this check)
- ⚠️ Max Action invocation count - Warning - Max number of allowed Action invocations for a single run (set value -1 to disable this check)
- ❌ Max Action invocation count - Error - Max number of allowed Action invocations for a single run (set value -1 to disable this check)
- ⚠️ Duration - Warning - The longest allowed run duration for the Workflow in milliseconds (set value -1 to disable this check)
- ❌ Duration - Error - The longest allowed run duration for the Workflow in milliseconds (set value -1 to disable this check)
Specific thresholds tab (Workflows)
For a specific Workflow, you can override the global settings.
The Specific thresholds tab lists the workflows that have their own thresholds.
- Name - The name of the Azure Workflow (note: case sensitive)
- Web Site Name - Conditional: The name of the Web Site with the specified Workflow (Applies only to the Standard App Service Plan)
- Resource Group Name - The name of the Resource Group with the Workflow
- Description - User friendly description for this configuration
- Clear DateTime (UTC) - The date time in UTC format to ignore Workflows that have previously failed (the lookback time span supersedes this value if too much time has passed); see also Clear
- Use global thresholds - When checked, the Monitoring thresholds use the global settings
Note
These are essentially the same as in the global settings and as such are not repeated in this documentation.
Example of a specific thresholds entry for one workflow.
Next Steps
- Add or manage a Monitoring Agent Configuration
- Add or manage Monitor View
- User access to Logic Apps Monitoring
- Back to Logging
- Back to Subscription configuration