Troubleshooting the Logic Apps Monitoring Agent

Use this troubleshooting FAQ to resolve Azure Logic Apps agent issues: agent startup, Diagnostic Settings, Event Hub, IIS, Windows Service, resources, monitor view issues, and event logs questions. If you still need help, contact our Support, read more on the Support page.

Understanding Where Problems Occur

Most problems sit on one hop of the path below. Find the symptom in the table, then check that hop first.

Data and control path of the Azure Logic Apps agent: logged events flow from the Diagnostic Settings through the Event Hub to the agent; the Monitoring Service asks the agent for state, and the agent reads Logic App state from Azure Resource Manager.

Pages in This Troubleshooting Section

How can I find my Azure Subscription details and add it to Nodinite?

Follow the steps outlined in the 'Azure Application Access' user guide, then add the subscription as described in Configuration - Subscription. For the minimum role set, see Azure Application Access - Least Privileges.

Cannot start the agent

Tip

Always ensure you are running the latest version of the agent. The Logic Apps Logging and Monitoring agent is built with .NET and receives monthly patches with vital updates and improvements. Download the latest version from the Nodinite portal and follow Updating.

Nodinite v7

The Logic Apps Logging and Monitoring agent runs in IIS and may have problems starting due to configuration or dependency issues. Your problem may stem from one or more of the following common configuration errors:

• IIS application pool not started or misconfigured; verify the IIS Windows Features
• Insufficient permissions for the application pool identity
• Missing or incorrect .NET runtime; see Software Requirements for the version your agent needs
• Prerequisites are not met, further detailed in the Prerequisites page
• Configuration errors in the agent settings; review the Configuration pages

Nodinite v6 (Legacy)

Note

The following troubleshooting steps apply to legacy v6 environments only. If you are running Nodinite v7, see the section above.

The Logic Apps Logging and Monitoring agent in v6 runs as a Windows service and may have problems starting due to security and run-time related dependencies. Your problem may stem from one or more of the following common configuration errors:

• Insufficient rights to run as a Windows Service, solution found in the following article: How to set Logon as a Service right
• Shared port error, a possible solution exists in the following article: Shared Port 8000
• Prerequisites are not met, further detailed in the Prerequisites page

Logic Apps not listed as Resources

• Access rights missing or incorrectly configured, solution found in the following article: Azure Application Access
• The subscription or its resource groups are not added to the agent configuration
• The Resources are not included in any Monitor View that you have access to

There is no logged data

• Make sure the Logic Apps have a Diagnostic setting that sends WorkflowRuntime to the Event Hub, as detailed in Enable Logic Apps Logging in Azure; the ARM Template deploys it for many Logic Apps at once
• Verify the Event Hub entry: the Event Hub name, the namespace fully qualified name, and the checkpoint Blob Container URI (or the connection strings, when the entry uses SAS keys)
• Verify that the App Registration has the Event Hub and Storage roles
• Make sure the firewall is open, review Troubleshoot connectivity issues - Azure Event Hubs
• Check that each Event Hub has its own checkpoint container
• Check that the Logging filters keep the runs and Actions you expect, and that the Logging Service processes the Log Events

There are no Actions available

• Make sure the Monitor View has Actions option checked, further detailed in the Add or manage Monitor View page
• Make sure your Roles grant access to the Remote Actions; see User access to logic apps monitoring and Managing Logic Apps

How can I lower the Azure cost of logging Logic Apps?

Shorten the Azure run-history retention and let Nodinite keep the long-term history, with Logging filters that keep only the Actions and payloads that matter. See Reduce Azure Logic Apps Run History Retention to Lower TCO. The cost of the Event Hub and checkpoint Storage is explained in Azure Costs for Blob Storage and Event Hub. If you also log Azure API Management or Azure Functions to Nodinite, see Reduce Azure API Management Logging Costs and Reduce Azure Functions Logging Costs.

Connectivity and Firewall Checks

Use this section when the agent cannot reach Azure or Nodinite services, or when logging appears to stop without an obvious agent error.

The ports and hostnames for every hop, from the Monitoring Service to the agent and from the agent to the Log API, SQL Server, and Azure, are in one place: Prerequisites - Firewall settings. Compare your firewall rules with those tables first.

Quick checks

• Use AMQP Port Configuration - 5671 and 5672 when Event Hub connectivity fails.
• Review Safelist the Azure portal URLs on your firewall or proxy server if Azure portal or management calls are blocked.
• Review Configure Azure Storage firewalls and virtual networks if Storage checkpointing fails.
• If events arrive but payloads are missing, check whether the workflows restrict run history access by caller IP address; the Agent Server's outbound IP address must be allowed.
• Remember that Azure communication is outbound from the agent, and stateful firewalls usually allow the response traffic automatically.

Frequently asked questions

How can I get started monitoring my Logic Apps?

This topic is further detailed in the User access to logic apps monitoring page. To give business users access to the logged data, see User access to logic apps logging.

Where do I install the agent?

You can install your Nodinite environment on existing hardware on-premise, on Azure Virtual machines, or have your sourcing partner host it in the cloud. Hybrid scenarios are also supported. See Install.

Tip

We recommend you install this agent on the same Server as Nodinite Core Services.

Uninstall Logic Apps Monitoring Agent

• Make sure the Agent is stopped before running the MSI package, further detailed in the uninstallation user guide
• You must be a local administrator to remove Windows Services

How do I get the latest version?

Download from the Nodinite portal, then follow Updating.

How do I know when there's a new version available?

Subscribe to updates using our Support portal.

How do I know where the agent is installed and running

Review the Nodinite Overview and/or the Monitor Agent Run-time Information section.

Next Steps

• Prerequisites - Review required Azure access, Event Hub settings, and Windows configuration.
• Install - Reinstall or verify the agent installation when troubleshooting startup issues.
• Configuration - Review the agent configuration for monitor view and resource problems.
• Update - Update to the latest version of the agent.

Related Topics

• Azure Logic Apps Logging and Monitoring agent
• Monitoring Logic Apps
• Logging Logic Apps
• Managing Logic Apps
• User access to logic apps monitoring
• User access to logic apps logging
• About Logic Apps Logging options
• ARM Template
• Uninstalling
• Reduce Azure Logic Apps Run History Retention to Lower TCO