- 5 minutes to read

Release Notes

Prerequisites for the Nodinite Web Services Monitoring Agent

Prepare your environment for seamless monitoring of Web Services and Web Applications with Nodinite. This page outlines all prerequisites for installing and running the Web Services Monitoring Agent, ensuring a smooth and secure deployment.

With Nodinite, you can:

  • Monitor any Web Service, Web Application, WCF, or Web API
  • Deploy agents on-premises or in the cloud, with flexible network options
  • Leverage secure Windows authentication and granular user rights
  • Automate monitoring with minimal firewall and network configuration

This page describes the prerequisites for installing and running the Nodinite Web Services Monitoring Agent.

graph LR subgraph "Web Servers" ro1(fal:fa-list Web Applications) end subgraph "APIs" roCloudAPI(fal:fa-cloud Web Services) end subgraph "Nodinite" roMonitoringService(fal:fa-watch-fitness Monitoring Service) -->roNI(fal:fa-code-commit Web Services Monitoring Agent) roNI --> ro1 roNI --> roCloudAPI end

This diagram shows how the Nodinite Web Services Monitoring Agent connects to web servers and APIs, managed by the Nodinite Monitoring Service.

You can install agent instances on the same network as Nodinite, or deploy them in the cloud/offsite using Service Bus Relaying (see also the external link for additional information 'Azure Relay FAQs').

We recommend that you keep this agent close to the Nodinite Server

Verified Topic
Software Requirements
What Windows User Rights does the Web Services Monitoring agent require?
What Firewall settings are required for the Web Services Monitoring agent?

Software requirements

Product
Windows Server Windows 2025
Windows 2022
Windows 2019
Windows 2016
Windows 2012 R2
Windows 2012
Windows 2008 R2
.NET Framework .NET Framework 4.8 or later New 6.0
Our recommendation is .NET Framework 4.8.1 or later

Versions 6.0 and later require .NET Framework 4.8 or later.
Versions 5.4 and later require .NET Framework 4.6.2 or later.
Versions before 5.4 require .NET Framework 4.5.2 or later.

What Windows User Rights does the Web Services Monitoring agent require?

The Web Services Monitoring Agent installs as a Windows Service—usually on the Nodinite application server—and runs with least possible privileges:

You can fine-tune access rights per Web Service/Web Application. Configure these individually—see the Configuration user guide for details.

What Firewall settings are required for the Web Services Monitoring agent?

The Web Services Monitoring agent uses both inbound and outbound communication:

graph LR subgraph "Web Servers" ro1(fal:fa-list Web Applications) end subgraph "Cloud Services" roCloudAPI(fal:fa-cloud APIs) end subgraph "Nodinite" roMonitoringService(fal:fa-watch-fitness Monitoring Service) -->|8000|roNI(fal:fa-code-commit Web Services Monitoring Agent) roNI -->|HTTP/HTTPS| ro1 roNI -->|HTTP/HTTPS| roCloudAPI end

This diagram illustrates the network and firewall communication paths for the Nodinite Web Services Monitoring Agent.

1. TCP Ports between the Monitoring Service and the Web Services 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 Nodinite Version Comment
53 DNS All 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 1a (Nodinite v7 - IIS hosted on local network)

Port Name Inbound Outbound TCP UDP Nodinite Version Comment
Custom HTTP/HTTPS v7 Agent IIS site port (configured during installation in the Portal). Only required if agent is on a remote IIS server

Note

Nodinite v7 IIS Hosting: When agents are hosted in IIS on the same server as the Nodinite application (typical installation), firewall rules are not required between the Monitoring Service and the agent. The custom port is assigned during installation via the Nodinite Portal and only needs to be opened if the agent is hosted on a remote IIS Windows Server.

Option 1b (Nodinite v6 and earlier - Windows Service on local network)

Port Name Inbound Outbound TCP UDP Nodinite Version Comment
8000 RPC v6 and earlier Communication is initiated by the Monitoring Service. Only used with legacy MSI installer on remote Windows servers

Note

Nodinite v6 Legacy: Port 8000 is only used when agents have default installations on remote Windows servers using the legacy MSI installer. This port is not required for Nodinite v7 IIS-hosted agents.

Option 2 (Cloud/Hybrid - All versions)

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 Nodinite Version Comment
443 HTTPS All Secure outbound traffic
5671, 5672 Secure AMQP All
9350 - 9354 Net.TCP All

2. Between the Web Services Monitoring Agent and Target Web Services

Server types: Agent Server (where Web Services Monitoring Agent is installed), Web Server (hosts the Web Services/Applications), Cloud API Endpoints (external HTTP/HTTPS services).

HTTP/HTTPS Connection (Agent → Web Services)

The agent initiates outbound connections to monitor the configured Web Services and Web Applications over HTTP or HTTPS.

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server Web Server / Cloud API TCP 80 (HTTP), 443 (HTTPS) Web Service monitoring requests Port may vary based on user configuration
Inbound Web Server / Cloud API Agent Server TCP 80 (HTTP), 443 (HTTPS) Response traffic Allowed automatically by stateful firewalls

Tip

Custom Ports: The actual port(s) depend on your Web Service/Application configuration. You must open whatever TCP port your services use. Common alternatives include 8080 (HTTP alternate), 8443 (HTTPS alternate), or custom ports like 9000, 3000, etc.

Tip

Cloud Services: For cloud-hosted APIs (Azure, AWS, etc.), ensure the Agent Server has outbound internet access on port 443 (HTTPS). No inbound rules are required on the cloud side.

Note

DNS Resolution: All servers (Agent Server and Web Servers) 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 solutions to common problems and FAQs for the Nodinite Web Service Monitoring Agent in the Troubleshooting user guide.

Next Step

Install Web Service Monitoring Agent

Configuration
Add or manage a Monitoring Agent Configuration
Monitoring
Administration