Manage Monitoring and Logging for Azure Logic Apps
Manage, monitor, and log your Azure Logic Apps with Nodinite, securely and without direct Azure Portal access.
What you will achieve with Nodinite:
- ✅ Secure, self-service management for business and IT users
- ✅ Advanced monitoring and logging for rapid troubleshooting
- ✅ Remote actions and configuration for streamlined operations
- ✅ Full audit trail for compliance and governance
| Application Management Team | IT Operations | Business |
|---|---|---|
| Let your AM team stop and start services independently | Stay in control with full access | Give your business Data and self-service for Logic Apps solutions |
Features
The Nodinite Azure Logic Apps Logging and Monitoring Agent offers the following features:
- Manage Monitoring thresholds
- Manage Logging options
- Perform Remote Actions
- Remote Configuration
The Roles of your Users control access through Monitor Views and Log Views; see User access to logic apps monitoring and User access to logic apps logging.
| Resource Name | Monitoring | Actions | Metrics/Statistics | |
|---|---|---|---|---|
| Subscription | ✅ Yes | Details | Statistics | |
| Resource Group | ✅ Yes | Details Inactivate | Statistics | |
| Logic App | ✅ Yes | Enable Disable Details Inactivate Edit thresholds View history | - | |
| Failed Runs | ✅ Yes | List failed runs Clear Resubmit | - | |
| Failed Triggers | ✅ Yes | List failed triggers Clear Resubmit | - | |
| Log Configuration | ✅ Yes | Details | - |
Info
All operations performed by you and other Users are logged to the Nodinite Audit Log, ensuring compliance with policies and regulations.
Remote Configuration
As an Administrator with access to Monitoring Agents, you can use the Remote Administration dialog to:
- Add, Remove, and Manage Azure subscriptions
- Add, Remove, and Manage Resource groups within each subscription
- Enable and Disable Monitoring
- Enable and Disable Logging
See Configuration for details.
Azure Subscription
Tip
Manage the set of Resource Groups included in Logging and Monitoring from the Subscription Details page.
The 'Subscription' Category provides a Resource for each configured Subscription, using the specified display name as the Resource name.
Example from a Monitor View with a list of configured Azure Subscriptions.
If you have permission to perform Remote Action, the following operations are available:
List of defined Remote Action
Subscription Details
To view and manage the selected Subscription Resource and its Resource Groups in Monitoring and Logging, click the Action button and select Details from the 'Control Center' menu.
Use the 'Details' action menu item to open the details modal for the selected Subscription.
Subscription details showing the selected resource groups, monitoring state, and logging options.
All available Resource Groups are listed (including those visible in Azure and those manually added in Configuration).
- Monitoring is enabled for checked Resource Groups. Check or uncheck the row to enable or disable monitoring.
- Logging can be enabled when Monitoring is enabled.
Tip
The list of Resource Groups can be filtered by typing in the filter text box.
Click Save to persist changes.
Save button used to persist subscription changes.
Subscription Statistics
To view statistics about Workflows in the selected Subscription Resource, click the Action button and select Statistics from the 'Control Center' menu.
Use the 'Statistics' action menu item to open the Statistics modal for the selected Subscription.
Statistics modal showing workflow totals and duration metrics for the selected subscription.
All Workflows in the Resource Groups for the current Configuration are shown in accordions.
Statistics table
The table lists Workflows and provides valuable details:
| KPI | Description |
|---|---|
| Max invocations | The Workflow Run with the most Action Invocations. This helps identify Workflows with excessive loops. For Consumption-based Workflows, this can indicate high costs. |
| Total invocations | Total number of Action Invocations. A large number may indicate a costly or resource-intensive Workflow. |
| Succeeded | Total number of successful runs. |
| Failures | Total number of failed runs. |
| Max Duration | Duration of the slowest run. |
| Min Duration | Duration of the fastest run. |
| Avg Duration | Average duration for all runs. |
| First run | Date of the oldest Workflow run. |
| Last run | Date of the most recent Workflow run. |
Resource Group
The Category 'Resource Group' provides a Resource for each Resource Group included in Monitoring.
Example of a filtered Monitor View with the Resource Group Category.
If you have permission to perform Remote Action, the following operations are available:
List of defined Remote Action.
Resource Group Details
To view the selected Resource Group Resource, click the Action button and select Details from the 'Control Center' menu.
Use the 'Details' action menu item to open the details modal for the selected Resource Group.
Example of the Details modal for a selected Resource Group.
Info
The data is logically the same for Logic Apps Standard and Consumption.
Inactivate Resource Group
If a Resource Group no longer exists in Azure, click Inactivate to remove it from Monitoring and Logging.
You can open the Details page even for unavailable Resource Groups.
Example of an Inactivated Resource Group.
Example of an Inactive Success Resource Group.
Resource Group Statistics
To view statistics about Workflows in the selected Resource Group Resource, click the Action button and select Statistics from the 'Control Center' menu.
Use the 'Statistics' action menu item to open the Statistics modal for the selected Resource Group.
Example of the Statistics modal for a selected Resource Group.
See the Statistics table for more information.
Logic App
The Category 'Logic App' provides a resource for each Logic App found in configured Azure Subscriptions.
Example from a Monitor View with Logic Apps included in Monitoring.
Info
See Monitoring Logic Apps for more details about Logic Apps Monitoring.
The following Remote Actions are available to users from Monitor Views Logic Apps where Remote Actions are allowed:
- Details
- Disable
- Edit thresholds
- Enable
- Inactivate
- View Run History
- View Trigger History
Remote Actions on the Logic App Category.
Logic App Details
To get details about a Workflow, click the Action button and select Details from the 'Control Center' menu.
Example of the Details Logic Apps sub menu item.
Example of a details page for a Workflow.
Note
Review the Diagnostic settings to ensure the agent configuration matches Azure and that Monitoring and Logging are operational.
Disable Logic App
To change the state of an enabled Logic App, click the Action button and select Disable from the 'Control Center' menu.
Example of the Disable Logic Apps sub menu item.
In the dialog, confirm or abort the action.
Dialog asking for confirmation to disable the named Logic App.
The outcome of the operation is then displayed.
Result from operation.
Edit thresholds Logic App
To change Monitoring thresholds, click the Edit thresholds sub menu item.
Example of the Edit thresholds Logic App sub menu item.
The Properties header in the Edit thresholds modal lets you manage:
| Field | Description |
|---|---|
| Description | A user-friendly description of the Workflow. |
| Last clear date time | Ignore execution errors before this time. |
Header for editing Monitoring thresholds for the selected Workflow.
The Thresholds section sets non-event Monitoring thresholds that override the global thresholds.
Set proper non-event Monitoring thresholds.
- Use global thresholds – When checked, the Workflow uses the global settings
- Lookback period – How far back in time to look; used when the current time is past the last clear date-time plus the lookback period
- ⚠️ Warning and ❌ Error values for Min execution count, Max execution count, and Max invocation count (-1 disables the check, the default), and for Duration (milliseconds)
Enable Logic App
To change the state of a disabled Logic App, click the Action button and select Enable from the 'Control Center' menu.
Example of the Enable Logic app sub menu item.
After clicking, a dialog asks for confirmation. Confirm or abort the operation.
Dialog asking for confirmation to enable the named Logic App.
The outcome of the operation is then displayed.
Result from operation.
Ignore Evaluation Errors
Remote action used to ignore evaluation errors for a specific workflow run.
Inactivate Logic App
When a Workflow is removed in Azure, Nodinite reports it as 🚫 Unavailable. Nodinite cannot tell whether the removal was intentional, so an Administrator must click Inactivate to stop monitoring it.
Important
Why Inactivate and NOT Exclude? With an exclusion, the agent keeps querying the Azure REST API for a Workflow that no longer exists, wasting API calls and bandwidth. Inactivate stops those calls.
Info
If the Workflow is redeployed, it will be detected and automatically reappear in Monitoring.
Example of the Inactivate Logic app sub menu item.
In the dialog, confirm or abort the action.
Dialog asking for confirmation to inactivate the named Logic App.
The outcome of the operation is then displayed.
Result from operation.
Warning
You cannot remove a Workflow if the system still believes it is present.
View Logic App Run History
To view Workflow run history, click the View history sub menu item. It shows what Azure still keeps; see Reduce Azure Logic Apps Run History Retention to Lower TCO.
Example of the View history Logic app sub menu item.
In the modal, you can Search by date. From any row, you can navigate to the run in Azure or use the Admin Log View (if you are an Administrator) to view Trigger and Action events according to your current Log Configuration.
Example with Workflow runs.
Failed Runs
If there are failed runs newer than the last Clear DateTime, the Logic App is listed with the ❌ Error Monitoring state, and Alarm Plugins notify the subscribers of the Monitor View. You can see the full list of failed runs since the last clear date.
For each Workflow, there is a Category 'Failed Runs'.
Example from a Nodinite Monitor View with Logic Apps in the Failed Runs Category.
The following Remote Actions are available:
Remote actions available for the Failed Runs category, including manage, clear, and resubmit operations.
Manage Failed Runs
Perform Action 'Manage failed runs' to get a list of failed runs for the selected Logic App.
View and manage information about failed runs.
On this screen, you have multiple features:
- Filter by error description.
Filter field used to narrow failed runs by their error description. - Actions Button
- Resubmit failed run – Rerun operation.
- Clear – Remove this run from the list. It is then available in the Logic App's History.
- Resubmit and Clear – Rerun and remove from the list.
Action menu used to resubmit, clear, or combine failed-run operations.
- Logging Information
- Failed Run Details
- Clear all Failed Runs
Resubmit failed run
Action to Resubmit a failed run.
Clear
To remove a failed run, use the Clear action.
A cleared failed run will eventually be removed from the database during cleanup.
Perform the Clear action to ignore this failed run.
When you click Clear, a dialog asks for confirmation.
Confirmation dialog shown before clearing a failed run.
Logging Information
As a Nodinite Administrator, clicking Correlation Id on any row opens the built-in Admin Log View in a new tab, with the System Interchange Id Search Field pre-populated.
Correlation identifier used to open the matching Admin Log View entry for the failed run.
The search shows All events for that run (they share the same interchange id).
Log event list showing all entries for the selected interchange identifier.
Clicking Action on any Log Event lets you view and download the payload.
Detailed log payload view for the selected failed interchange.
Failed Runs Details
Click the small button to the left of Actions to display more information about the Failed Run.
Details button used to inspect more information about the selected failed run.
Clear all Failed Runs
Clear all Failed Runs, available in multiple places, excludes all failed runs from Failed Runs Monitoring, but they remain available in the Logic App's History.
Failed Triggers
For each Workflow, the 'Failed Triggers' Category lists failed triggers, with the same List, Clear, and Resubmit Remote Actions as Failed Runs.
Log Configuration
Each Subscription has one Log Configuration Resource. This Resource is part of Monitoring and any detected problem is presented accordingly.
Example of the Log Configuration Resource.
You can use the following Remote Actions to interact with the current Log Configuration:
Example with available Actions on the Log Configuration Resource.
Log Configuration Details
To view details for the current Log Configuration on the selected Subscription, click the Actions button and select Details.
The Details sub menu item.
On the Details page, the header presents information about the Subscription and current vital Log Configuration. Expand the accordion.
Example modal with details about the current Log Configuration.
Manage Diagnostics Settings
To add or update Diagnostics settings, use the Nodinite Log Configuration Category, click the Actions button, and select Manage diagnostic settings.
The action used to open the diagnostics settings editor for the selected subscription.
To apply the same diagnostic setting to many Workflows, use an ARM Template instead; About Logic Apps Logging options explains which categories to enable.
Example modal used to create or update diagnostics settings for Logging and Monitoring with Nodinite.
- Name – The name of the diagnostics setting
- SAS Policy ARM ID – The resource ID for a SAS Policy to access the Event Hub
Field used to enter the SAS Policy ARM ID required for Azure Event Hub access. - Logic Apps
- Either the Logic App Standard service plan, or (applies to ALL Workflows in this instance)
- Individual Consumption-based Workflow
- Event Hub Name – The target entity name of the Event Hub for Azure Diagnostics
Note
You must configure the Nodinite Azure Logic Apps Logging and Monitoring Agent and match the Azure diagnostics configuration with the listener (this agent).
Frequently asked questions
See the Troubleshooting user guide for solutions to common problems and the FAQ.
Note
To manage your Logic Apps from Nodinite, you must enable Monitoring of Logic Apps, as described in the configuration page
Next Steps
- Configure Message Types - Make your Logic Apps data searchable and enable advanced features
- User access to logic apps monitoring - Give teams self-service through Monitor Views
Related Topics
- Azure Logic Apps Overview
- Message Types - Critical for Search Field extraction from Logic Apps events
- Search Fields - Extract business data from Logic Apps messages
- Non-Events Monitoring - Track message volumes and patterns
- BPM - End-to-end process tracking across Logic Apps and other systems