eG Help

The 24x7 availability of the Connection Broker is imperative to ensure that end-users have uninterrupted access to desktops/data and critical computing resources. A Connection Broker might be rendered unavailable owing to many reasons - eg., an internal configuration error, a database error, the non-availability of the Connection Broker's web interface, etc. While the knowledge of the failure of a Connection Broker is valuable to an administrator, knowing what caused the failure can alone help the administrator quickly resolve the issue and restore the Connection Broker to normalcy. The CBStatusTest instantly informs administrators of the non-availability (if any) of the Connection Broker, reports whether it is owing to the web service being down, and also intimates them of any probable slowdown in the responsiveness of the server. The measures made by this test are as follows:

Measurement	Description	Measurement Unit	Interpretation
CB_availability	This measure indicates whether/not the Connection Broker service is available.	Percent	The value 100 indicates that the Connection Broker is available. If the value is 0, it indicates that the Connection Broker is not available. This could be owing to an internal error, or if the database is inaccessible, or a poor network connection.
Web_availability	Indicates whether the web server part of the Connection Broker is available or not.	Percent	The value 100 indicates that the web server is available. If the value is 0, it indicates that the web server is not available. In the event of the non-availability of the Connection Broker, you can use the value of this measure to determine whether the Connection Broker failure occurred because the web server was deliberately/inadvertently stopped or had failed due to some errors.
Response_time	Indicates the time taken by the Connection Broker to respond to requests.	Secs	Ideally, this value should be low. Sporadic spikes or a steady increase in this value is a cause for concern as it indicates deterioration in the performance of the Connection Broker. This could be owing to improper configuration of the broker or when the broker experiences an overload.