- 5 minutes to read

Prerequisites for the Nodinite Non-Events Monitoring Agent

Unlock the full power of Nodinite by meeting all prerequisites for the Non-Events Monitoring Agent. This guide gives you a clear, actionable checklist so you can install and run the agent with confidence—empowering your business with proactive, reliable monitoring.

✅ Follow a step-by-step prerequisites checklist for seamless installation
✅ Meet all Windows, .NET, and firewall requirements for secure operation
✅ Empower your team with clear guidance for configuration and user rights
✅ Visualize agent connectivity and network requirements for rapid troubleshooting

graph LR subgraph "Nodinite Instance" roNI(fal:fa-monitor-waveform Non Events Monitoring Agent) --> roAzureAPI(fal:fa-cloud-arrow-down Web API) end

This diagram shows how the Non-Events Monitoring Agent connects to the Web API within your Nodinite instance.

Install the agent close to Nodinite Core Services. This documentation guides you through a typical local network setup, usually on the Nodinite application server.

Verified Topic
Software Requirements
What Windows User Rights does the Non-Events Monitoring Agent require?
What Firewall settings are required for the Non Events Monitoring Agent?

Software Requirements

Install the Non-Events Monitoring Agent as a robust Windows Service, typically on the Nodinite application server for optimal performance and security.

Product
Windows Server Windows 2025
Windows 2022
Windows 2019
Windows 2016
Windows 2012 R2
Windows 2012
.NET Framework .NET Framework 4.8 or later. New 6.0.0.0
We recommend .NET Framework 4.8.1 for hosts running Nodinite components.

You must use .NET Framework 4.8 or later for versions 6.0 and above.
Use .NET Framework 4.6.2 or later for versions 5.4 and above.
Use .NET Framework 4.5.2 or later for versions prior to 5.4.

Supported Versions

Keep Nodinite and the Non-Events Monitoring Agent up to date to ensure compatibility with the latest Web API.

Subscribe to our Release Notes so you never miss an important update!

What Windows User Rights does the Non-Events Monitoring Agent require?

Install the agent as a Windows Service on the Nodinite application server or a supported virtual machine.

What Firewall settings are required for the Non-Events Monitoring Agent?

Where you install the Nodinite Non-Events Monitoring Agent in relation to the Nodinite Monitoring Service and the Web API determines your firewall configuration. The agent evaluates Non-Events by querying Log Views through the Web API. The diagram shows every host involved, with the agent on its own server; each arrow starts at the side that opens the connection.

graph LR subgraph "Nodinite Core Services Server" roMonitoringService(fa:fa-watch-fitness Monitoring Service) roWebAPI(fa:fa-cloud-arrow-down Web API) end subgraph "Nodinite Agent Server" roNI(fa:fa-monitor-waveform Non-Events Monitoring Agent) end subgraph "Identity Provider (optional)" roIdP(fa:fa-id-card OAuth 2.0 / OIDC token endpoint) end subgraph "Domain Controller" roDC(fa:fa-id-badge Active Directory) end subgraph "DNS Server" roDNS(fa:fa-signs-post DNS) end roMonitoringService --> |"Agent site port (v7) / 8000 (v6)"| roNI roNI --> |"Web API site port"| roWebAPI roNI -.-> |"443"| roIdP roNI -.-> |"88, 389, 636 (Windows auth)"| roDC roNI --> |"53"| roDNS

Network diagram: the Monitoring Service calls the agent, and the agent queries Log Views through the Web API, authenticating with Windows authentication or an OAuth 2.0 / OIDC token. Dashed arrows are optional hops.

Note

When the agent runs on the Core Services Server (the typical installation), you need no firewall rule between the Monitoring Service or the Web API and the agent.

Between the Monitoring Service and the Non-Events Monitoring Agent

The Monitoring Service opens every connection; the agent never calls it. On Windows Server, Nodinite v7 hosts the agent as its own IIS web site, on a port you set per environment in the Nodinite Portal (Servers step).

Direction Source Destination Protocol Port(s) Purpose Notes
Inbound Core Services Server Agent Server TCP (HTTPS/HTTP) Agent site port Poll the agent, send configuration, run Remote Actions v7. No fixed default; use the port set in the Portal. Only when the agent is on a remote server
Inbound Core Services Server Agent Server TCP 8000 Same, for Windows Service agents ⚠️ v6 and earlier only (legacy MSI installer on remote servers)

Between the Non-Events Monitoring Agent and the Web API

The agent calls the Log View API URI of each configuration (Configuration). In v7, the Web API is its own IIS web site (https://{host}:{port}/api/...), on a port you set per environment in the Portal (Servers step).

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server Core Services Server TCP (HTTPS/HTTP) Web API site port Query Log Views for Non-Events and ACK/NAK evaluation v7. No fixed default; use the port in the Log View API URI. Use HTTPS in production
Inbound Core Services Server Agent Server TCP Web API site port Response traffic Automatically allowed by stateful firewall inspection

Between the Non-Events Monitoring Agent and the Identity Provider

Required only with OAuth 2.0 / OIDC authentication, when Nodinite v7 uses OpenID Connect.

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server Identity Provider (token endpoint) TCP (HTTPS) 443 Request access tokens (client credentials) Host of the configured IDP token endpoint, for example login.microsoftonline.com for Microsoft Entra ID

Between the Non-Events Monitoring Agent and the Domain Controller

Required with Windows authentication or Windows impersonation (domain accounts) against the Web API.

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server Domain Controller TCP/UDP 88 Kerberos authentication Required for domain authentication
Outbound Agent Server Domain Controller TCP/UDP 389 LDAP Standard LDAP queries
Outbound Agent Server Domain Controller TCP 636 LDAPS (Secure LDAP) Required for LDAPS authentication
Inbound Domain Controller Agent Server TCP/UDP Same as outbound Response to Kerberos / LDAP Usually allowed by stateful firewall inspection

Between the servers and DNS

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server DNS Server TCP/UDP 53 Name resolution Resolve the Core Services Server (Web API), the Domain Controller, and the Identity Provider. A local hosts file can replace DNS for on-premises hosts
Outbound Core Services Server DNS Server TCP/UDP 53 Name resolution Resolve the Agent Server

Important

Stateful Firewalls: Most Windows Firewall implementations are stateful, so response traffic for established outbound connections is allowed automatically. The inbound response rules above are for reference and troubleshooting.

Frequently Asked Questions

Find more solutions and answers to common questions in the Troubleshooting guide for the Nodinite Non-Events Monitoring Agent.

Next Steps

Install Non-Events Monitoring Agent

Add or manage a Monitoring Agent Configuration
Monitoring
Administration