Multi-Server

HZN Queue Console is built for teams that run multiple broker environments. You can connect to as many servers as you need — production, acceptance, test, local — and switch between them without restarting the app.

The Server Panel

The left-hand server panel lists all your configured connections. Each entry shows:

The server name you gave it
An environment badge (PROD, ACC, TEST, DEV, LOCAL) colour-coded for at-a-glance safety
An optional group label to cluster related servers
Live connection status

Click any server to make it the active connection. All views switch to that broker immediately.

Environment Badges

Colour-coded environment badges are a deliberate safety feature. The colours are:

Environment	Colour
PROD	Red
ACC	Orange
TEST	Yellow
DEV	Blue
LOCAL	Green

When you’re connected to a production server the entire app header highlights in red to reduce the risk of accidentally routing messages or making changes on the wrong server.

Groups

Use the Group field when adding a server to organise connections in the panel. Servers with the same group label are visually clustered together. Useful for projects that have separate brokers per microservice or per region.

Example groups: Payments cluster, EU region, Legacy infra.

Monitoring Across Servers

The Monitoring view can display queues from multiple servers on the same chart. This lets you compare queue depths across environments side by side — for example, watching production and acceptance fill and drain in parallel during a release.

Routing Across Servers

Message routing is always within a single server — you cannot route a message directly from a production queue to a test queue in one step. To move a message across servers, export it from the source queue and import/publish it to the target.