Solace System Health Test
The performance and stability of the Solace PubSub+ Event Broker may be affected by the performance and stability of the underlying system resources. By monitoring the health of the target Solace PubSub+ Event Broker, system administrators can analyze the infrastructure and assess the system resources assigned to the event broker at runtime. Administratorscan then use this information to correlate event broker performance and stability issues with other infrastructure events, and assess the suitability of the infrastructure for event broker deployments.
This test monitors the health of the target Solace PubSub+ Event Broker and reports the latencies (disk / network / compute) that are hindering the performance and stability of the target event broker.
Target of the test : A Solace PubSub+ Event Broker
Agent deploying the test : A remote agent
Outputs of the test : One set of results for the target Solace PubSub+ Event Broker that being monitored
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The IP address of the target host for which this test is to be configured. |
Port |
Refers to the port at which the Solace PubSub+ Event Broker listens to. |
UserName and Password |
By default, the eG agent executes SEMP ( Solace Element Management Protocol) APIs on the target broker to collect the required metrics. For the eG agent to execute the SEMP APIs, a special user with read only privilege is required. Specify the credentials of such a user in the UserName and Password text boxes. To know how to create such a user, refer to Creating a New User for Monitoring Solace PubSub+ Event Broker. |
Confirm Password |
Confirm the Password by retyping it in the Confirm Password text box. |
SSL |
By default, this flag is set to No indicating that the Solace PubSub+ Event Broker is not SSL-enabled by default. Set this flag to Yes if the Solace PubSub+ Event Broker is SSL-enabled. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Disk latency |
Indicates the time taken by the disk to read and write messages that are subscribed to. |
Milliseconds |
Disk I/O latency statistics are collected wherever latency may affect performance and the monitoring does not significantly impact performance or stability. The software event broker raises an asynchronous event when measured disk I/O latency exceeds the configured threshold value. A high latency may indicate that the disk, or access to the disk, is oversubscribed. |
Mate-link latency |
Indicates the overall time taken to access the subscribed messages. |
Milliseconds |
This metric measures the completion time of a transaction over the mate-link, and is an aggregate metric as the mate-link transaction combines compute, disk, and network latencies. This is a direct metric with significant impact on the overall stability of a high-availability (HA) group. The software event broker raises an asynchronous event when the measured mate-link latency exceeds the configured threshold. |
Compute latency |
Indicates the time taken by the CPU to respond to read and write subscribed messages. |
Milliseconds |
This metric compares the execution time of well-known functions (for example, epoll timers) against invariant timers (for example, CPU TSC). A high latency may indicate that the CPU is oversubscribed, the CPU is being blocked by another application, or access to virtual memory is somehow degraded. The software event broker raises an asynchronous event when measured latency for CPU instructions exceeds the configured threshold value. |
Network latency |
Indicates the time taken to transmit/receive subscribed messages over the network. |
Milliseconds |
This metric measures the round trip network transaction latency (for example, for a ping operation) between the instance and members of its high-availability (HA) group. A high latency may indicate a faulty or misconfigured physical network interface, inadequate or faulty network cabling, a network storm/loop, or an over utilized network. The software event broker raises an asynchronous event when the measured network latency exceeds the configured threshold value. |