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. 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, 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 |
Set the thresholds once for all workflows on the Global thresholds tab, and override them for individual workflows on the Specific thresholds tab.
Workflows tab
Enter settings in the Workflows tab for specifics.
General Tab (Workflows)
- Enable monitoring of Workflows - When checked, Workflows for enabled Resource groups(s) will be monitored
- Enable trigger evaluation of Workflows - When checked, triggers for enabled workflows will be monitored
- 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.
Global Thresholds (Workflows)
You can configure Non-Events type Monitoring. This option is easier to use on the Logic App Resource.
- 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.
- 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 has previously failed (the look back time span will supersede this value if too long time has passed)
- Use global thresholds - When checked, the Monitoring thresholds uses the global settings
Note
These are essentially the same as in the global settings and as such are not repeated in this documentation.
Next Steps
- Add or manage a Monitoring Agent Configuration
- Add or manage Monitor View
- Back to Logging
- Back to Subscription configuration