eG Monitoring
 

Measures reported by QpidBrokerTest

The Apache Qpid Java Broker is a powerful open-source message broker that implements all versions of the Advanced Message Queuing Protocol (AMQP). AMQP is an open internet protocol for reliably sending and receiving messages. It makes it possible for everyone to build a diverse, coherent messaging ecosystem. This test reports the current state of the broker, ensuring that there is a proper message transaction happening to and from the broker and also alerts the administrators on memory constraints, if any.

Outputs of the test: One set of results for the target Apache Qpid Java Broker.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
state Indicates the current state of the broker.  

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
Stopped 0
Quiesced 50
Uninitialized 60
Unavailable 70
Errored 80
Deleted 90
Active 100

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the current state of the broker.

Use the detailed diagnosis of this measure to figure out the Process PID details.

dataIn It indicates the total size of all the messages received by the Broker. MB

A very low value is desired for this measure since more number of messages can exceed the size of the broker’s internal buffer, causing unexpected errors.

dataOut It indicates the total size of all the messages delivered by the Broker. MB

 

dirMemoryTotalCapacity It indicates the total capacity of direct memory allocated for the Broker process. MB

A very high value is desired for this measure. When the broker detects that it uses 75% of available direct memory it will start flowing incoming transient messages to disk and reading them back before delivery. This will prevent the broker from running out of direct memory but may degrade performance by requiring disk I/O.

inboundMsgeSizeHghWtrMrk It indicates the maximum size of messages published into the Broker since start-up. MB

 

messagesIn It indicates the total number of messages received by the Broker. Messages

 

messagesOut It indicates the total number of messages delivered by the Broker. Messages

 

numberOfBuffersInPool It indicates the number of unused direct memory buffers currently available in the pool. Counts

A very high value is desired for this measure.

numberOfBuffersInUse It indicates the number of direct memory buffers currently in-use. Counts

A very low value is desired for these measures.

numberOfLiveThreads It indicates the number of live threads. Counts

A very low value is desired for these measures.

nmbrOfObjctPendingFinal It indicates the number of objects to be finalized. Counts

Ideally, the value of this measure should be zero.

processCpuLoad It indicates the CPU load of the current process. Counts

A very low value is desired for these measures.

processCpuTime It indicates the CPU time of the cumulative process. Milliseconds

A very low value is desired for these measures.

transactedMessagesIn It indicates the total number of messages received by the Broker within a transaction. Messages

A very high value is desired for these measures. A transactional message is an automated message that’s triggered by an action a given consumer takes. Generally these messages include necessary or high-priority info, such as a receipt, delivery details or updates, or order confirmations - and because they’re triggered by that individual's unique actions, they’re always sent on an individual basis, rather than to a big list of potential recipients.

transactedMessagesOut It indicates the total number of messages delivered by the Broker within a transaction. Messages

A very high value is desired for these measures. A transactional message is an automated message that’s triggered by an action a given consumer takes. Generally these messages include necessary or high-priority info, such as a receipt, delivery details or updates, or order confirmations - and because they’re triggered by that individual's unique actions, they’re always sent on an individual basis, rather than to a big list of potential recipients.

usedDirectMemorySize It indicates the size of used direct memory. MB

A very low value is desired for this measure.

usedHeapMemorySize It indicates the size of used heap memory. MB

A very high value is desired for this measure. When the broker runs low on heap memory, performance will degrade because the JVM will trigger full garbage collection (GC) events in a struggle to free memory.