- 5 minutes to read

Release Notes

Prerequisites for the Nodinite RabbitMQ Monitoring agent

Get ready to unlock seamless RabbitMQ monitoring with Nodinite! This page guides you through all prerequisites for installing and running the Nodinite RabbitMQ Monitoring Agent. You'll gain:

✅ Real-time visibility into your RabbitMQ clusters
✅ Proactive alerts for issues before they impact business
✅ Flexible deployment—on-premise, cloud, or hybrid
✅ Secure, reliable integration with minimal latency

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

Diagram: The Nodinite RabbitMQ Monitoring Agent connects securely to one or more RabbitMQ nodes within a cluster, whether on-premise or in the cloud, to provide comprehensive monitoring and management.

You can deploy the agent on-premise (using TCP/IP for local network access) or in the cloud/off-site using Service Bus Relaying. For hybrid or distributed environments, this flexibility ensures you always have secure, reliable access to your RabbitMQ resources.

💡Best Practice: Install the agent as close as possible to your RabbitMQ cluster nodes for optimal performance and minimal latency.

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 Supported Versions
Windows Server Windows 2025; Windows 2022; Windows 2019; Windows 2016; Windows 2012 R2; Windows 2012; Windows 2008 R2
.NET Framework .NET Framework 4.6.2 or later; Recommended: .NET Framework 4.8

Versions prior to 5.4 require .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 and evaluate the state of your RabbitMQ queues, disk, and memory. The agent must have appropriate access rights.

Supported Versions

RabbitMQ evolves rapidly as an open-source project. Nodinite always supports the APIs currently maintained by RabbitMQ. To ensure compatibility and security, regularly update both Nodinite and the RabbitMQ Monitoring Agent.

Stay informed—subscribe to our Release Notes.

What Windows User Rights does the RabbitMQ Monitoring agent require?

The agent runs as a Windows Service—typically on the Nodinite application server. Virtual machines are fully supported.

What Firewall settings are required for the RabbitMQ Monitoring agent?

The RabbitMQ Monitoring Agent requires both inbound and outbound communication:

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

Diagram: Communication flows between the Nodinite Monitoring Service, the RabbitMQ Monitoring Agent, and the RabbitMQ API/nodes, highlighting required ports and network paths.

1. Between the Monitoring Service and the RabbitMQ Monitoring Agent

Allow the following ports 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 must resolve server/service addresses (optionally via local hosts file)

Choose either Option 1 or Option 2 below, depending on your deployment:

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 different networks.

Nodinite uses the same principle as the On-Premise data gateway. See 'Adjust communication settings for the on-premises data gateway'.

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 RabbitMQ Monitoring Agent and RabbitMQ Servers

The following section details firewall requirements organized by service. Two types of servers participate:

  • Agent Server - Where the Nodinite RabbitMQ Monitoring Agent is installed
  • RabbitMQ Server - RabbitMQ nodes and Management API being monitored

RabbitMQ Management API Connection (Agent → RabbitMQ Server)

Required for connecting to the RabbitMQ Management HTTP API to monitor queues, exchanges, connections, and cluster health.

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server RabbitMQ Server TCP 15672 RabbitMQ Management API Default HTTP port for Management plugin. HTTPS uses port 15671
Inbound RabbitMQ Server Agent Server TCP 15672 Response traffic Automatically allowed by stateful firewall inspection

Note

DNS Resolution: All 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.

Tip

RabbitMQ Clustering: If monitoring a RabbitMQ cluster with multiple nodes, ensure the Agent Server can reach the Management API on all nodes. The Management plugin must be enabled on at least one node.

Tip

HTTPS/SSL: If your RabbitMQ Management API uses HTTPS (port 15671), adjust the firewall rules accordingly. The default HTTP port is 15672.

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 more solutions and answers in the Troubleshooting guide for the Nodinite RabbitMQ Monitoring Agent.

Next Step

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

Administration
Monitoring Agents