- 4 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?

Configure the Non-Events Monitoring Agent to communicate both inbound and outbound for seamless monitoring:

  1. Let the Monitoring Service communicate with the Non-Events Monitoring Agent.
  2. Let the Non-Events Monitoring Agent communicate with the Web API.
graph LR subgraph "Nodinite Instance" roMonitoringService(fal:fa-watch-fitness Monitoring Service) roNI(fal:fa-monitor-waveform Non Events Monitoring Agent) roMonitoringService --> |8000/443| roNI roNI --> |80/443| roWebAPI(fal:fa-cloud-arrow-down Web API) end

This network diagram shows the required communication paths and ports for the Non-Events Monitoring Agent.

1. Between the Monitoring Service and the Non-Events Monitoring Agent

Allow the following ports on the Windows server where you install and run the agent:

Port Name Inbound Outbound TCP UDP Comment
53 DNS The Agent resolves server/service addresses (optionally via local hosts file)

Choose either 'Option 1' or 'Option 2' as documented below:

Local network

Port Name Inbound Outbound TCP UDP Comment
8000 RPC The Monitoring Service initiates communication

2. Between the Non-Events Monitoring Agent and Nodinite Web API

Server types: Agent Server (where Non-Events Monitoring Agent is installed), Web API Server (Nodinite Web API).

Web API Connection (Agent → Nodinite Web API)

The agent sends monitoring data to the Nodinite Web API for processing and storage.

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server Web API Server TCP 80 (HTTP), 443 (HTTPS) Web API communication Agent sends monitoring data
Inbound Web API Server Agent Server TCP 80 (HTTP), 443 (HTTPS) Response traffic Allowed automatically by stateful firewalls

Tip

Custom Ports: The Nodinite Web API can be configured to use any available TCP port. Verify the actual port in your Web API configuration and adjust firewall rules accordingly.

Tip

HTTPS Recommended: For production environments, configure the Web API to use HTTPS (port 443) with valid SSL/TLS certificates to encrypt monitoring data in transit.

Note

DNS Resolution: All servers (Agent Server and Web API Server) require outbound access to DNS on TCP/UDP port 53 for name resolution. This is already listed in section 1 and applies universally. You can optionally solve this using entries in the local hosts file on each server.

Important

Stateful Firewalls: Most modern Windows Firewall implementations are stateful, meaning inbound response traffic for established outbound connections is automatically allowed. The inbound rules listed above are primarily for reference and troubleshooting scenarios where stateful inspection may be disabled or restricted.

Frequently Asked Questions

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

Next Step

Install Non-Events Monitoring Agent

Add or manage a Monitoring Agent Configuration
Monitoring
Administration