Release Notes
Prerequisites for the Nodinite Web Services Monitoring Agent
This page describes the prerequisites for successfully installing and running the Nodinite Web Services Monitoring Agent.
Instances of this agent can be installed on the same network where Nodinite is installed, however, Nodinite can also be installed elsewhere, like in the cloud/offsite using Service Bus Relaying (see also the external link for additional information Microsoft Service Bus Relaying - External Link).
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 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 make use of the .NET Framework 4.8 or later.
Versions 5.4 and subsequently make use of the .NET Framework 4.6.2 or later.
Versions before 5.4 make use of the .NET Framework 4.5.2 or later.
What Windows User Rights does the Web Services Monitoring agent require?
The Web Services Monitoring Agent is installed as a Windows Service usually on the Nodinite application server and can be run with least possible privileges:
- Local named account or domain account (preferred). Follow this guide 'How to set Logon as a Service right' for more information.
You can fine tune access rights needed per Web Service/Web Applications and is configured individually, review the Configuration user guide for additional details
What Firewall settings are required for the Web Services Monitoring agent?
The Web Services Monitoring agent has both inbound and outbound communication:
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 | 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 is 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. TCP Ports between Nodinite Web Services Monitoring Agent and Web Services
| 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 with user-defined entries in the hosts file in each Windows server instance), review the following 'Microsoft' user guide |
||||
| 80 | HTTP | default for HTTP) | ||||
| 443 | HTTPS | default for HTTPS |
The actual port may depend on user configuration and you must open whatever TCP port your Web Services and Web Applications are using
Frequently asked questions
Additional solutions to common problems and the FAQ for the Nodinite Web Service Monitoring Agent exist in the Troubleshooting user guide.
Next Step
Install Web Service Monitoring Agent
Related
Configuration
Add or manage a Monitoring Agent Configuration
Monitoring
Administration