The table below lists the resource types in vRealize Hyperic that map to managed RabbitMQ entities. The right column indicates the inventory level for each type in the vRealize Hyperic inventory model.

Table 1. RabbitMQ Entities

Hyperic Resource Type


Hyperic Inventory Type


A RabbitMQ broker, also referred to as a node, is an implementation of an Advanced Message Queuing Protocol (AMQP) broker. It is a configurable entity that listens for messages on a TCP/IP port.

A broker is represented in Hyperic as a "RabbitMQ" server.


RabbitMQ Exchange

A RabbitMQ exchange is a resource that routes messages to queues.

An exchange is represented in Hyperic as a "RabbitMQ Exchange" service.


RabbitMQ Queue

A queue is a resource that stores and forwards messages to message consumers.

A queue is represented in Hyperic as a "RabbitMQ Queue" service.


RabbitMQ VirtualHost

A virtual host serves as a name-spacing mechanism for queues and exchanges on a broker. A broker always has a default virtual host identified by a forward slash character ( /). Additional virtual hosts can be explicitly configured on a broker. The same queue (or exchange) name in two virtual hosts on denotes a different resource in each virtual host.

RabbitMQ's first level of access control is enforced at the virtual host level; if a user attempts to connect to a virtual host to which he does not have credentials, the a broker rejects the connection attempt.

A RabbitMQ virtual host is represented in Hyperic as a "RabbitMQ VirtualHost" service.


RabbitMQ Connection

A physical connection e.g. using TCP/IP or SCTP. A connection is bound to a user.


RabbitMQ Channel

A logical connection that is tied to a connection.