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
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.
Tip
Install the agent as close as possible to your RabbitMQ cluster nodes for optimal performance and minimal latency.
Software Requirements
Versions 7.0.4 and later require .NET 10 Hosting Bundle.
| Product | Supported Versions |
|---|---|
| Windows Server | Windows 2025; Windows 2022; Windows 2019; Windows 2016; Windows 2012 R2; Windows 2012 |
| .NET 10 Hosting Bundle New 7.0.4 | Required for v7.0.4 and later. Download from Microsoft |
| .NET Framework | .NET Framework 4.6.2 or later; Recommended: .NET Framework 4.8 |
Versions 7.0.4 and later require .NET 10 Hosting Bundle.
.NET 10 minimum OS: Windows Server 2012 / 2012 R2. Windows Server 2008 R2 is supported only for legacy versions (<=7.0.3) running on .NET Framework.
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.
Service Account Options New 7.0.4:
- Group Managed Service Account (gMSA) - Recommended for automated password management. See Configure Group Managed Service Accounts (gMSA) for setup instructions.
- Traditional Account - Use a local named account or (preferably) a domain account.
- Follow the 'How to set logon as a Windows service right' guide for step-by-step instructions.
What Firewall settings are required for the RabbitMQ Monitoring agent?
Where you install the Nodinite RabbitMQ Monitoring Agent in relation to the Nodinite Monitoring Service and your RabbitMQ nodes determines your firewall configuration. The diagram shows every host involved, with the agent on its own server; each arrow starts at the side that opens the connection.
Network diagram: the Monitoring Service calls the agent, and the agent calls the RabbitMQ Management HTTP API. Dashed arrows are optional hops.
Note
When the agent runs on the Core Services Server (the typical installation), you need no firewall rule between the Monitoring Service and the agent.
Between the Monitoring Service and the RabbitMQ Monitoring Agent
The Monitoring Service opens every connection; the agent never calls it. On Windows Server, Nodinite v7 hosts the agent as its own IIS web site, on a port you set per environment in the Nodinite Portal (Servers step).
| Direction | Source | Destination | Protocol | Port(s) | Purpose | Notes |
|---|---|---|---|---|---|---|
| Inbound | Core Services Server | Agent Server | TCP (HTTPS/HTTP) | Agent site port | Poll the agent, send configuration, run Remote Actions | v7. No fixed default; use the port set in the Portal. Only when the agent is on a remote server |
| Inbound | Core Services Server | Agent Server | TCP | 8000 | Same, for Windows Service agents | ⚠️ v6 and earlier only (legacy MSI installer on remote servers) |
Option: Service Bus Relaying (cloud or hybrid)
Use Service Bus Relayed connections when Nodinite and the agent are on different networks. Both sides connect outbound to the Azure Relay namespace, so neither server needs an inbound rule. Nodinite uses the same principle as the on-premises data gateway; see 'Adjust communication settings for the on-premises data gateway' and the 'Azure Relay FAQs'.
| Direction | Source | Destination | Protocol | Port(s) | Purpose | Notes |
|---|---|---|---|---|---|---|
| Outbound | Agent Server | Azure Relay (*.servicebus.windows.net) |
TCP | 443 | HTTPS | All versions |
| Outbound | Agent Server | Azure Relay (*.servicebus.windows.net) |
TCP | 5671, 5672 | Secure AMQP | All versions |
| Outbound | Agent Server | Azure Relay (*.servicebus.windows.net) |
TCP | 9350 - 9354 | Net.TCP | All versions |
| Outbound | Core Services Server | Azure Relay (*.servicebus.windows.net) |
TCP | 443, 5671, 5672, 9350 - 9354 | Monitoring Service side of the relay | Same ports as the Agent Server |
Between the RabbitMQ Monitoring Agent and RabbitMQ
Required for monitoring queues, exchanges, connections, and cluster health through the RabbitMQ Management HTTP API (the API Uri in the Configuration guide). The RabbitMQ networking guide lists 15672 and 15671 as the management plugin ports.
| Direction | Source | Destination | Protocol | Port(s) | Purpose | Notes |
|---|---|---|---|---|---|---|
| Outbound | Agent Server | Target (RabbitMQ node) | TCP (HTTP) | 15672 | RabbitMQ Management HTTP API | Default port of the Management plugin |
| Outbound | Agent Server | Target (RabbitMQ node) | TCP (HTTPS) | 15671 | RabbitMQ Management HTTP API over TLS | When the Management plugin uses HTTPS (see SSL/TLS support) |
| Inbound | Target (RabbitMQ node) | Agent Server | TCP | 15672, 15671 | Response traffic | Automatically allowed by stateful firewall inspection |
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.
Between the servers and DNS
| Direction | Source | Destination | Protocol | Port(s) | Purpose | Notes |
|---|---|---|---|---|---|---|
| Outbound | Agent Server | DNS Server | TCP/UDP | 53 | Name resolution | Resolve the RabbitMQ nodes, the Core Services Server, and (with relaying) *.servicebus.windows.net. A local hosts file can replace DNS |
| Outbound | Core Services Server | DNS Server | TCP/UDP | 53 | Name resolution | Resolve the Agent Server |
Important
Stateful Firewalls: Most Windows Firewall implementations are stateful, so response traffic for established outbound connections is allowed automatically. The inbound response rules above are for reference and troubleshooting.
Frequently asked questions
Find more solutions and answers in the Troubleshooting guide for the Nodinite RabbitMQ Monitoring Agent.
Next Steps
Add or manage a Monitoring Agent Configuration
Install the RabbitMQ Monitoring agent