Supported Brokers
HZN Queue Console connects to message brokers via their HTTP management APIs.
RabbitMQ
Minimum version: 3.11
Requirements:
- The
rabbitmq_managementplugin must be enabled. - The management API is available on port
15672(HTTP) or15671(HTTPS) by default. - The connecting user must have the
managementoradministratortag.
Features:
- Queue browser and message inspection
- Message filtering by header, routing key, payload content
- Message routing and DLQ rescue (with
x-deathcleanup) - AsyncAPI schema validation
- Table view and column presets
- Queue monitoring (message count, consumer count, memory)
ActiveMQ Classic
Minimum version: 5.16
Requirements:
- The web console / Jolokia REST API must be enabled (enabled by default in most distributions).
- Management port default:
8161.
Features:
- Queue browser and message inspection
- Basic message filtering
- Message routing between queues
ActiveMQ Artemis
Minimum version: 2.28
Requirements:
- The web console must be enabled (enabled by default).
- Management port default:
8161.
Features:
- Queue browser and message inspection
- Basic message filtering
- Message routing between queues
Cloud-Managed Brokers
Cloud-managed services (Amazon MQ, CloudAMQP, etc.) expose the same management APIs as self-hosted versions. HZN Queue Console works with these services provided:
- The management API port is accessible from your machine (check firewall and security group rules).
- You use the credentials provided by the service.
- HTTPS is typically required — use
https://as the scheme in the hostname field.
More Brokers
Additional broker support is on the roadmap. Check the changelog to see when new brokers are added.
Related
- Server Connections — connecting to a broker
- Connection Problems — diagnosing connection errors