Qpid Virtual Hosts Test
A virtual host is a container in which messaging is performed. Virtual hosts are independent; the messaging that goes on within one virtual host is independent of any messaging that goes on in another virtual host. For instance, a queue named Q1 defined in one virtual host is completely independent of a queue named Q1 in another virtual host. A virtual host is identified by a name which must be unique broker-wide. Clients use the name to identify the virtual host to which they wish to connect when they connect. A virtual host exists in a virtual host node and this virtual host comprises a number of entities. This test helps the administrators to monitor whether/not the current state of the virtual host is active, ensuring that the virtual host is performing proper messaging service.
Target of the test : Apache Qpid Java Broker
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for each Virtual Host in the target Apache Qpid Java Broker.
| Parameter | Description |
|---|---|
|
Test period |
How often should the test be executed. |
|
Host |
The IP address of the target server that is being monitored. |
|
Port |
The port number through which the Apache Qpid Java Broker communicates. The default port is 8080. |
|
Username |
By default, the eG agent executes REST APIs on the target component to collect the required metrics. For the eG agent to execute the REST APIs, a user with monitoring privilege is required. Specify the name of such a user in this text box. |
|
Password |
Specify the password corresponding to the user mentioned in the Username text box here. |
|
Confirm Password |
Confirm the password by retyping it here. |
|
SSL |
By default, the SSL flag is set to No, indicating that the target Apache Qpid Java Broker is not SSL-enabled by default. To enable the test to connect to an SSL-enabled Apache Qpid Java Broker, set the SSL flag to Yes. |
|
Timeout |
Specify the duration (in seconds) within which the query executed by this test should time out in this text box. |
|
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
| Measurement | Description | Measurement Unit | Interpretation | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
State |
Indicates the current state of this virtual host. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the current state of this virtual host. Use the detailed diagnosis of this measure to figure out the ID, Name and Description details. |
||||||||||||||||
|
Data evacuated from memory |
Indicates the total size of messages evacuated from memory. |
MB |
A very low value is desired for these measures. |
||||||||||||||||
|
Data in |
Indicates the total size of all messages received by this virtual host. |
MB |
|||||||||||||||||
|
Data out |
Indicates the total size of all messages delivered by this virtual host. |
MB |
|
||||||||||||||||
|
Connection count |
Indicates the current number of messaging connections to this virtual host. |
Counts |
A very high value is desired for these measures since connections to a virtual host can operate on exchanges, queues and bindings in that virtual host.
|
||||||||||||||||
|
Exchange count |
Indicates the current number of exchanges on this virtual host. |
Counts |
|||||||||||||||||
|
In memory message size |
Indicates the current size of all messages cached in-memory. |
MB |
A very low value is desired for this measure. |
||||||||||||||||
|
Inbound message size high watermark |
Indicates the maximum size of message published into the Virtual Host since broker start-up. |
MB |
|
||||||||||||||||
|
Messages in |
Indicates the total number of messages received by this virtual host. |
Messages |
|
||||||||||||||||
|
Messages out |
Indicates the total number of messages delivered by this virtual host. |
Messages |
|
||||||||||||||||
|
Queue count |
Indicates the current number of queues on this virtual host. |
Counts |
A very high value is desired for these measures.
|
||||||||||||||||
|
Total connection count |
Indicates the total number of messaging connections to this virtual host since broker start up. |
Counts |
|||||||||||||||||
|
Total depth of data queues |
Indicates the current size of all messages enqueued by this virtual host. |
MB |
|
||||||||||||||||
|
Total depth of queues messages |
Indicates the current number of messages enqueued by this virtual host. |
Messages |
|
||||||||||||||||
|
Transacted messages in |
Indicates the total number of messages delivered by this virtual host 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. |
||||||||||||||||
|
Transacted messages out |
Indicates the total number of messages received by this virtual host within a transaction. |
Messages |
