- 3 minutes to read

Release Notes

Prerequisites for the Nodinite RabbitMQ Monitoring agent

This page describes the prerequisites to successfully install and run the Nodinite RabbitMQ Monitoring Agent.

graph LR subgraph "Nodinite Instance" roNI(fal:fa-monitor-waveform RabbitMQ Monitoring agent) end subgraph "RabbitMQ Cluster" roRMQ(fal:fa-list RabbitMQ Node 1) roRMQ2(fal:fa-list RabbitMQ Node n) roNI --- roRMQ roNI --- roRMQ2 end

Instances of this agent can 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)

We recommend that you keep this agent close to the RabbitMQ Cluster nodes to monitor.

Verified Topic
Software Requirements
What RabbitMQ user rights does the RabbitMQ Monitoring agent require?
What Windows User Rights does the RabbitMQ Monitoring agent require?
What Firewall settings are required for the RabbitMQ 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.6.2 or later New 5.4
Our recommendation is .NET Framework 4.8

Versions prior to 5.4 make use of the .NET Framework 4.6.1 or later.

What RabbitMQ user rights does the RabbitMQ Monitoring agent require?

  • The agent uses the RabbitMQ API to retrieve information to evaluate the state of your RabbitMQ Queues, Disk and memory. Therefore the agent needs access rights.

Supported Versions

RabbitMQ is an Open Source project and is evolving fast. Nodinite will always support the API's currently supported. This means you need to update Nodinite and our 'RabbitMQ Monitoring agent' from time to time.

Make sure to subscribe to our Release Notes

What Windows User Rights does the RabbitMQ 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 RabbitMQ Monitoring agent?

The RabbitMQ Monitoring agent has both inbound and outbound communication:

  1. Between the Monitoring Service and the RabbitMQ Monitoring agent
  2. Between the RabbitMQ Monitoring agent and RabbitMQ Management API
graph LR subgraph "Nodinite Instance" roMonitoringService(fal:fa-watch-fitness Monitoring Service) roNI(fal:fa-monitor-waveform RabbitMQ Monitoring agent) roMonitoringService --> |8000| roNI end subgraph "RabbitMQ Environment" roRMQAPI(fal:fa-cloud RabbitMQ API)---roLA(fal:fa-clouds RabbitMQ nodes) roNI --> |15672| roRMQAPI end

1. Between the Monitoring Service and the RabbitMQ 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. Between the RabbitMQ Monitoring agent and RabbitMQ API

Port Name Inbound Outbound TCP UDP Comment
15672 Remote connection port Default for the API

Note

This port depends on customizable settings

Frequently asked questions

Additional solutions to common problems and the FAQ for the Nodinite RabbitMQ Monitoring Agent exist in the Troubleshooting user guide.

Next Step

Add or manage a Monitoring Agent Configuration
Install the RabbitMQ Monitoring agent

Administration
Monitoring Agents