Prerequisites for the Non Events Monitoring Agent
This page describes the prerequisites for successfully installing and running the Non Events Monitoring Agent.
Instances of this agent should be installed on-premise using TCP/IP for local network access and/or in the cloud/off-site using Service Bus Relaying (see also the external link for additional information MicrosoftServiceBusRelayingLink) as long as the Log API can be accessed on the configured port.
Our recommendation is to 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 Log 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 initiated by the Monitoring Service|
Use Service Bus Relayed connections when Nodinite and the agent are on totally different networks.
Nodinite uses the same principle technique as the On-Premise data gateway, see 'Adjust communication settings for the on-premises data gateway' user guide.
|443||HTTPS||Secure outbound traffic|
|5671, 5672||Secure AMQP|
|9350 - 9354||Net.TCP|
|80||HTTP||default for HTTP)|
|443||HTTPS||default for HTTPS)|
Note1: The Log API allows for the use of any available port and therefor the table above may not reflect your actual run-time configuration
Note2: If the Non Events Monitoring Agent and the Log API is on the same server you should stick with http for performance and information is not outside the server