Detailed information about the queues used by the Data Hub can be seen in the RabbitMQ management console.
WARNING: the management console also allows functional alteration of components of RabbitMQ, which could adversely affect the Data Hub or cause data loss. To prevent unwanted changes to RabbitMQ, you may want to create a monitoring user.
Note: The management console updates its display every 5 seconds, at the fastest, so queue state as shown in the console may be inaccurate. Additionally, rates listed are not guaranteed to accurately reflect the state of the Data Hub, depending on load and configuration. To mitigate these issues, use the the WMI Counters to monitor state, instead.
To access the management console's queues page:
guestas both the username and password.
This page displays all the queues used by this installation of RabbitMQ. All queues related to the Data Hub begin with the
pahub. prefix. If another application is using this instance of RabbitMQ (such as the PreEmptive Analytics Workbench),
there may be additional queues for that product.
pahub.endpoint queue is the Endpoint Queue, where the Endpoint Web Service queues all incoming messages for the Dispatch Service to process. Other queues represent destination-specific queues; for instance,
pahub.commercial ri_offline is
the Offline Queue for a destination named
The columns in this display are:
Note: These rates are only from the perspective of the queues themselves. Some operations by the Dispatch Service involve dequeuing and then re-queueing messages to a different queue (such as when a message from the endpoint queue is routed to an offline destination) or the same queue (such as after a retry of a message). To see the rates at which messages are actually being dispatched, use the WMI counters.
More detailed information for a particular queue can be found by clicking on the queue name from the queues page. This page is divided into sections. Of them, only the Overview section is relevant to monitoring - the other sections either provide no useful information for this application, or actively modify the queue rather than just observing it, often in potentially dangerous ways.
The Overview section is further divided into three subsections: