- 3 minutes to read

Release Notes

Prerequisites for the Nodinite Non-Events Monitoring Agent

This page describes the prerequisites to successfully install and run the Nodinite Non-Events Monitoring Agent.

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

We recommend that you keep this agent close to Nodinite Core Services. This documentation covers 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

The Non-Events Monitoring Agent is a Windows Service and is usually installed on the Nodinite application server.

Product
Windows Server Windows 2022
Windows 2019
Windows 2016
Windows 2012 R2
Windows 2012
.NET Framework .NET Framework 4.8 or later. New 6.0.0.0
Our recommendation is to use .NET Framework 4.8.1 on hosts with Nodinite components.

Versions 6.0 and later make use of the .NET Framework 4.8 or later.
Versions 5.4 and later make use of the .NET Framework 4.6.2 or later.
Versions prior to 5.4 make use of the .NET Framework 4.5.2 or later.

Supported Versions

Nodinite is evolving fast, and sometimes the Web API gets changed. This means you need to update Nodinite and our Non-Events Monitoring Agent from time to time.

Make sure to subscribe to our Release Notes.

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

The agent is installed as a Windows Service usually on the Nodinite application server. Virtual machines are supported.

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

The Non-Events Monitoring Agent has both inbound and outbound communication:

  1. Between the Monitoring Service and the Non-Events Monitoring Agent
  2. Between the Non-Events Monitoring Agent and 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-download Web API) end

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

The following ports must be allowed on the Windows server where the agent is installed and running :

Port Name Inbound Outbound TCP UDP Comment
53 DNS The Agent needs to know where your other servers/services are (can sometimes optionally be solved using entries in the local hosts file)

And further with 'Option 1' or 'Option 2' as documented next:

Local network

Port Name Inbound Outbound TCP UDP Comment
8000 RPC Communication is initiated by the Monitoring Service

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

Port Name Inbound Outbound TCP UDP Comment
80 HTTP default for HTTP
443 HTTPS default for HTTPS

Note1: The Web API allows for the use of any available port and therefor the table above may not reflect your actual run-time configuration

Frequently asked questions

Additional solutions to common problems and the FAQ for the Nodinite Non-Events Monitoring Agent exist in the Troubleshooting user guide.

Next Step

Install Non-Events Monitoring Agent

Add or manage a Monitoring Agent Configuration
Monitoring
Administration