Last updated

Prerequisites for the Non Events Monitoring Agent

This page describes the prerequisites for successfully installing and running the Non Events Monitoring Agent.

graph LR subgraph "Nodinite Instance" roNI(fal:fa-heart-rate Non Events Monitoring Agent) end subgraph "Azure Cloud / Subscriptions" roAzureAPI(fal:fa-cloud Microsoft Azure API)---roLA(fal:fa-clouds Your Logic Apps) roNI --> |REST| roAzureAPI end

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)

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 Windows 2019
Windows 2016
Windows 2012 R2
Windows 2012
.NET Framework .NET Framework 4.5 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 Log API
graph LR subgraph "Nodinite Instance" roMonitoringService(fal:fa-watch-fitness Monitoring Service) roNI(fal:fa-heart-rate Non Events Monitoring Agent) roMonitoringService --> |8000/443| roNI roLogAPI(fal:fa-cloud-download Log API) end subgraph "Azure Cloud / Subscriptions" roAzureAPI(fal:fa-cloud Microsoft Azure API)---roLA(fal:fa-clouds Your Logic Apps) roNI --> |443| roAzureAPI roNI --> |80,443| roLogAPI 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:

Option 1 (Local network)

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

Option 2 (Cloud/Hybrid)

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.

Port Name Inbound Outbound TCP UDP Comment
443 HTTPS Secure outbound traffic
5671, 5672 Secure AMQP
9350 - 9354 Net.TCP

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

Port Name Inbound Outbound TCP UDP Comment
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


Frequently asked questions

Common problems and FAQ for the Non Events Monitoring Agent can be found in the troubleshooting page.

Next Step

Install Non-Events Monitoring Agent

Add or manage a Monitoring Agent Configuration
Monitoring
Administration