Prerequisites for the Nodinite Non Events Monitoring Agent
This page describes the prerequisites for successfully installing and running the Nodinite Non Events Monitoring Agent.
We recommend that you keep this agent close to Nodinite Core Services. This documentation covers local network setup (usually on the Nodinite application server)
|What Windows User Rights does the Non Events Monitoring Agent require?|
|What Firewall settings are required for the Non Events Monitoring Agent?|
The Non Events Monitoring Agent is a Windows Service and is usually installed on the Nodinite application server.
Windows 2012 R2
|.NET Framework||.NET Framework 4.5 or later|
Make sure to subscribe to our Release Notes
The agent is installed as a Windows Service usually on the Nodinite application server. Virtual machines are supported.
- Local named account or domain account (preferred).
- Access and run-time rights
- Follow the 'How to set logon as a Windows service right' user guide for detailed instructions.
The Non Events Monitoring Agent has both inbound and outbound communication:
- Between the Monitoring Service and the Non Events Monitoring Agent
- Between the Non Events Monitoring Agent and the Web API
The following ports must be allowed on the Windows server where the agent is installed and running :
|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:
|8000||RPC||Communication is initiated by the Monitoring Service|
|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