Connection Broker Logs Test

The Connection Broker maintains a record of all activities it performs in log files. The logs show the different stages of user connection - e.g., when a user signs in, is offered and assigned a Desktop, logs out, etc. Using the logs, administrators can:

Diagnose problems with your policy logic related to power and assignment controls, by looking at logs related to powering up and down Desktops, and releasing desktops back to the pool.
Monitor the system load, such as the number of logins over a period of time.
Monitor user access

This test monitors the logs and alerts administrators to error/warning events that are captured by the logs.

Target of the test : A Leostream Connection Broker

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each of the Connection Broker logs being monitored.

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed.
Host	Specify the IP address of the Connection Broker for which the test is to be configured.
Port	Refers to the port used by the Connection Broker is listening.
SSL	By default, this flag is set to No, indicating that by default, the test connects to the Connection Broker via HTTP. If the Connection Broker is SSL-enabled, then set this flag to Yes.
User	To enable the test to log into the Connection Broker and extract statistics of interest from it, specify the login name of a user on the Connection Broker who is assigned the Administrator role. If need be, you can even create a special Administrator user on the Connection Broker for this purpose, and pass the credentials of that user to the test. Refer to Pre-requisites for Monitoring the Leostream Connection Broker to know how to create such a user.
Password	Specify the password of the user here.
Confirm Password	Confirm the password by retyping it here.
Timeout	Specify the duration (in seconds) within which the test should timeout. The default duration is 30 seconds.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency.
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: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Information events	Indicates the number of information events that were logged in the log currently.	Number	The detailed diagnosis of this measure reveals the details of the information events.
Warnings	Indicates the number of warning events recorded in the log, currently.	Number	Ideally, this value should be 0. If a non-zero value is reported, use the detailed diagnosis capability of this measure to know more about the warning event.
Errors	Indicates the number of error events that were currently recorded in the log.	Number	Ideally, this value should be 0. A non-zero value warrants further investigation. You can then use the detailed diagnosis capability of this measure to know more about the error event.