Prerequisites for the Nodinite RabbitMQ Monitoring agent

Prepare your environment for success! This page details everything you need to install and run the Nodinite RabbitMQ Monitoring Agent—empowering you with real-time visibility, proactive alerts, and seamless integration for your RabbitMQ clusters.

Mermaid 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.

Software Requirements

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.

• Use a local named account or (preferably) a domain account.
• Ensure the account has access and run-time rights.
  • 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?

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

Mermaid 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:

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

Option 1 (Local network)

Option 2 (Cloud/Hybrid)

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'.

2. Between the RabbitMQ Monitoring Agent and RabbitMQ API

Note

This port depends on customizable settings

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

Related Topics

Administration
Monitoring Agents