Troubleshooting the Nodinite Azure Monitoring Agent
Use this guide to resolve issues and get answers to your questions about the Nodinite Azure Monitoring Agent. Whether you are a systems integration expert or a new user, you find troubleshooting steps, FAQs, and support resources here.
- ✅ Find solutions to common installation and configuration problems
- ✅ Locate the failing hop, from the Monitoring Service to Azure
- ✅ Get direct links to support and documentation for fast resolution
- ✅ Empower your team to self-serve and minimize downtime
If you cannot resolve an issue, 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.
runs Remote Actions"| AG["fa:fa-monitor-waveform Azure Monitoring Agent
IIS (v7) or Windows Service (v6)"] AG -->|"token"| ENTRA["fa:fa-key Microsoft Entra ID
App Registration"] AG -->|"HTTPS 443"| ARM["fa:fa-cloud Azure Resource Manager
and service APIs"] MS --> MV["fa:fa-display Monitor Views
Resources and Actions"]
Control path of the Azure Monitoring Agent: the Monitoring Service asks the agent for state; the agent signs in with the App Registration and reads Azure. The ports for every hop are in Prerequisites - Firewall.
| Symptom | Hop to check | Go to |
|---|---|---|
| Agent does not start | Agent host (IIS in v7, Windows Service in v6) | Cannot start the agent |
| No Web Jobs or other Azure services in Monitor Views | App Registration and Azure Resource Manager | Resources not listed |
| Actions menu is empty | Monitor View settings and Roles | There are no Actions available |
| Connection errors | Firewall or proxy on any hop | Prerequisites - Firewall |
Pages in This Troubleshooting Section
| Page | Use it when |
|---|---|
| Uninstalling | You remove the agent |
| Updating | You update the agent |
| Monitoring Agents Troubleshooting | Install, diagnostics, and multiple instances for any Monitoring Agent |
How can I enable Azure Monitoring?
- Prepare the App Registration and network as described in Prerequisites, following the 'Azure Application Access' user guide and its least-privilege role set.
- Install the Nodinite Azure Monitoring Agent.
- Configure the agent through Remote Configuration; see Configuration.
Cannot start the agent
Tip
Always run the latest version of the agent; download it from the Nodinite portal and follow Updating.
Nodinite v7
On Windows Server, Nodinite v7 hosts the Azure Monitoring Agent as its own IIS web site. Check these common configuration errors:
- The IIS application pool is stopped or misconfigured; verify the IIS Windows Features
- The application pool identity lacks rights; see Prerequisites - Windows rights
- The .NET runtime is missing; see Prerequisites - Software
- Prerequisites are not met; see Prerequisites
Nodinite v6 (Legacy)
The v6 agent runs as a Windows service and may not start if it lacks required security or runtime dependencies. Check these common configuration errors:
- Make sure the account has rights to run as a Windows Service—see: How to set Logon as a Service right
- Resolve any shared port error—see: Shared Port 8000
- Meet all prerequisites—see: Prerequisites
The Web Jobs are not listed as Resources
The same check applies to every Azure service the agent monitors, such as Functions or Storage:
- Verify access rights are present and correctly configured—see: Azure Application Access and Prerequisites - Azure rights
- Verify that the service is selected in the agent Configuration
- Verify that a Monitor View includes the Resources by Category or Application
There are no Actions available
- Enable the Remote Actions privilege in the Monitor View. See the Add or manage Monitor View page for details.
- Check that your Role has access to that Monitor View.
Frequently asked questions (FAQ)
Where do I install the agent?
You can install your Nodinite environment on existing on-premise hardware, on Azure Virtual Machines, or in the cloud with your sourcing partner. Hybrid scenarios are also supported.
We recommend you install this agent on the same Windows Server as Nodinite Core Services.
Uninstall Nodinite Azure Monitoring Agent
- Stop the Agent before you run the MSI package—see the uninstallation user guide.
- Use a local administrator account to remove Windows Services.
How do I get the latest version?
Download the latest version from the Nodinite portal.
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 the Monitor Agent Run-time Information section.
How many Azure subscriptions can one agent monitor?
Unlimited. A single agent instance can monitor hundreds of subscriptions, thousands of resource groups, and tens of thousands of resources—with one Nodinite license.
Do I need to grant users Azure portal access?
No. Nodinite provides role-based self-service access to Azure resources through Monitor Views without granting Azure Reader or Contributor roles. Users authenticate to Nodinite, not Azure.
What Azure RBAC roles does the agent require?
Typically Reader role on subscriptions plus specific action permissions (e.g., restart Web Jobs, manage queue messages). See Prerequisites - Azure rights and Azure Application Access for least-privilege guidance.
Can I monitor Azure Government or Azure China regions?
Yes. Configure the agent with the appropriate Azure cloud endpoints (AzureUSGovernment, AzureChinaCloud, etc.) during installation.
How does the agent authenticate to Azure?
Through an Azure App Registration (Service Principal) with Client ID and Client Secret/Certificate. No user passwords or shared credentials required. All API calls use Microsoft Entra ID (Azure AD) authentication.
Can I monitor Azure resources in different Azure AD tenants?
Yes. Configure multiple App Registrations—one per tenant—and the agent monitors resources across all tenants from one Nodinite instance.
Does the agent work with Azure Private Link or Private Endpoints?
Yes. The agent can monitor services behind Private Endpoints as long as network connectivity exists between the agent server and the private endpoint IP addresses. See Prerequisites - Firewall for networking requirements.
How does Function monitoring work with Application Insights?
The agent executes custom Kusto queries against Application Insights to retrieve Function execution metrics, failures, and traces. You configure the queries to match your telemetry schema. See Monitoring Function for details.
What's the difference between this agent and the Azure Logic Apps agent?
This agent monitors Azure infrastructure services (Functions, Storage, Event Hubs, API Management, etc.). The Azure Logic Apps agent is a dedicated agent for Logic App workflows with specialized logging and monitoring capabilities for connectors, actions, and triggers.
Next Steps
- Install the Azure Monitoring Agent
- Read the Configuration guide for the Azure Monitoring Agent
- Review the Prerequisites for Azure Monitoring