Manage Monitoring and Logging for Azure Logic Apps
Unlock the full potential of your Azure Logic Apps with Nodinite. This page guides you through comprehensive management, monitoring, and logging—empowering your teams to work efficiently and securely, all 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
Manage logging, monitoring thresholds, and perform administrative remote actions on Logic Apps for configured Azure Subscriptions.
| 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
| Resource Name | Monitoring | Actions | Metrics/Statistics | |
|---|---|---|---|---|
| Subscription | ✔️ | Details | Statistics | |
| Resource Group | ✔️ | Details Inactivate | Statistics | |
| Logic App | ✔️ | Enable Disable Details Inactivate Edit thresholds View history | - | |
| Failed Runs | ✔️ | List failed runs Clear Resubmit | - | |
| Failed Triggers | ✔️ | List failed triggers Clear Resubmit | - | |
| Log Configuration | ✔️ | 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 the global Configuration for more details about configuring Nodinite and the Azure Logic Apps Logging and Monitoring Agent.
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.
Next, click the option to present the modal.
All available Resource Groups are listed (including those visible in Azure and those manually added in Configuration).
Monitoring is enabled for checked Resource Groups. You can enable or disable monitoring by checking or unchecking the row.
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.
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.
Next, click the option to present the modal.
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 virtual Resource for each configured Subscription.
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.
Next, click the option to present the modal.
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.
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.
Next, click the option to present the modal.
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
Example of Remote Actions available 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 allows you to set non-event Monitoring thresholds.
Set proper non-event Monitoring thresholds.
Use global thresholds – When checked, use the global Monitoring settings for this Workflow
Lookback period – How far back in time to look. Monitoring uses this if the current time is greater than the last clear date-time plus the lookback period
Min execution count (Warning)
Min execution count (Error)
Enter thresholds for count-based evaluation. -1 disables the check (default)Max Execution count
Max execution count (Warning)
Max execution count (Error)
Enter thresholds for count-based evaluation. -1 disables the check (default)Max invocation count (Warning)
Max invocation count (Error)
Enter thresholds for count-based evaluation. -1 disables the check (default)Duration Warning
Duration Error
Set the threshold for maximum duration in 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
Inactivate Logic App
When a Workflow is removed in Azure, Nodinite automatically detects its absence and reports it as Unavailable. Since the system cannot determine if the removal was intentional, the Nodinite Administrator must Inactivate Monitoring. Click Inactivate to remove active monitoring for the Workflow.
Important
Why Inactivate and NOT Exclude?
It is crucial to Inactivate missing resources rather than simply excluding them. Excluding a Workflow means the agent continues to query the Azure REST API for information that no longer exists, resulting in unnecessary API calls, wasted bandwidth, and increased resource consumption. Inactivating ensures the agent stops fetching data for absent resources, optimizing performance and reducing operational overhead. This best practice is vital in large-scale or regulated environments where efficiency and resource management are paramount.
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.
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. 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:
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.
- 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.
- 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.
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 pre-populated.
The search will start, showing All events for that run (same interchange id for all events).
Clicking Action on any Log Event lets you view and download the payload.
Failed Runs Details
Click the small button to the left of Actions to display more information about the Failed Run.
Clear all Failed Runs
The Clear all Failed Runs option is available in multiple places for convenience. Clearing all failed runs excludes them from Failed Runs Monitoring, but they remain available in the Logic App's History.
Failed Triggers
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 Details sub menu item.
On the Details page, the header presents information about the Subscription and current vital Log Configuration.
Example modal to manage Diagnostics to enable 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
- 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
Additional solutions to common problems and the FAQ for the Nodinite Azure Logic Apps Logging and Monitoring Agent are available in the Troubleshooting user guide.
Note
To manage your Logic Apps from Nodinite, you must enable Monitoring of Logic Apps, as described in the configuration page