Horizon Cluster/Pod Events Test

The events database stores information about View events as records in a database rather than in a log file. This database serves as a rich source of information on the status of and problems encountered by Omnissa Horizon Connection Servers in the Omnissa Horizon Cluster/Pod. Using the Horizon Cluster/Pod Events test, administrators can periodically query the events database for the count of errors, warnings, general information, success and failure events stored in it, and also view the details of such events. With the help of these details, administrators can easily and effectively troubleshoot issues affecting the operations of Omnissa Horizon Connection Server.

Target of the test : An Omnissa Horizon Cluster/Pod

Agent deploying the test : A remote agent

Outputs of the test : One set of results for the Omnissa Horizon Cluster/Pod being monitored

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed
Host	The host for which the test is to be configured
Port	Refers to the port used by the Omnissa Horizon Cluster/Pod. The default port number is NULL.
Using Horizon API	By default, this flag is set to Yes indicating that this test will use the Omnissa Restful API to collect the required metrics. Alternately, if you wish to collect the metrics by querying the Microsoft SQL database server where the events are stored, set this flag to No.
Connection Server Name	This parameter will appear only when the Using Horizon API flag is set to Yes. By default, this test connects to every Horizon Connection Server configured in the Omnissa Horizon Cluster/Pod remotely and collects the required metrics. For this, it is necessary to specify valid credentials of the Horizon Connection Servers. To help administrators provide these credentials quickly and easily, the eG administrative interface embeds a special configuration page. To access this page, simply click on the encircled '+' icon that appears alongside this parameter in the test configuration page. To know how to use this special page, refer to Configuring the Omnissa Horizon Connection Servers for Monitoring.
User Name, Password and Confirm Password	These parameters will appear only when the Using Horizon API flag is set to Yes. By default, this test uses Omnissa Restful APIs to collect the required metrics from the target Omnissa Horizon Cluster/Pod. For this, the eG agent should be configured with read-only user privileges that will allow the agent to communicate with the Horizon Connection Server in a particular domain and extract statistics. Therefore, specify the credentials of the user who is authorized to access the Horizon Connection Server against the User Name, Password and Confirm Password text boxes.
Domain Name	This parameter will appear only when the Using Horizon API flag is set to Yes. Specify the name of the domain to which the Horizon Connection Server belongs to.
DatabaseType	This parameter will appear only when the Using Horizon API flag is set to No. Specify the type of the database in the DatabaseType text box. By default, the DatabaseType is Microsoft SQL.
DatabaseServer	This parameter will appear only when the Using Horizon API flag is set to No. Specify the IP address of the database server that holds the Omnissa Horizon Connection Server event database.
DatabasePort	This parameter will appear only when the Using Horizon API flag is set to No. Specify the port of the database server.
Instance	This parameter will appear only when the Using Horizon API flag is set to No. Specify the instance name of the Omnissa Horizon Connection Server event database. By default, this is set to none.
EventsDatabaseName	This parameter will appear only when the Using Horizon API flag is set to No. Specify the name of the database that holds the Omnissa Horizon Connection Server events.
EventsTableName	This parameter will appear only when the Using Horizon API flag is set to No. By default, the Omnissa Horizon View events are stored in an event table in the Omnissa Horizon Connection Server events database. The name of the event table can be identified as the name specified against the Table Prefix field in the Omnissa Horizon Connection Server console. This name should be explicitly appended with the word 'event' and specified against the EventsTableName parameter. For example, if your Table Prefix is D3022A, then, you should specify D3022Aevent against this parameter.
User and Password	These parameters will appear only when the Using Horizon API flag is set to No. Provide the credentials of the user who has the authorization to execute queries on the Events Database.
Confirm Password	This parameter will appear only when the Using Horizon API flag is set to No. Confirm the password by retyping it here.
Domain	This parameter will appear only when the Using Horizon API flag is set to No. Specify the name of the domain in the Domain text box.
SSL	This parameter will appear only when the Using Horizon API flag is set to No. By default, the SSL flag is set to No. If the Microsoft SQL server that is hosting the Events Database is SSL-enabled, set this flag to Yes.
Exclude Messages	By default, this is set to none. Specify a comma-separated list of patterns that you wish to exclude from the scope of monitoring in this text box. These patterns should be a specific keyword that appears in the description of the events that are generated. For example your pattern specification can be: warning, message.
Show Info DD	By default, this flag is set to No, indicating that this test will not report detailed diagnostics for the Information measure. This means that, by default, eG will not capture and store the complete details of information messages in the eG database. This default setting is ideal, as in the real world, hundreds of information messages will be written to the events database, and by not writing the details of these messages in the eG database, considerable database space can be saved. However, if your eG database is well-sized and you prefer to view the description of all the information messages that are written to the events database, then set this flag to Yes.
Show Audit Success DD	By default, this flag is set to No, indicating that this test will not report detailed diagnostics for the Audit success measure. This means that, by default, eG will not capture and store the complete details of successful audit events in the eG database. This default setting is ideal, as in the real world, numerous audits will be successful, and by not writing the details of these successful events in the eG database, considerable database space can be saved. However, if your eG database is well-sized and you want to view the description of all the successful audit events that are written to the events database, then set this flag to Yes.
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 messages	Indicates the total number of information events in the database.	Number	For complete details of the information events, use the detailed diagnosis of this measure.
Errors	Indicates the total number of error events in the database.	Number	For complete details of the error events, use the detailed diagnosis of this measure.
Warnings	Indicates the total number of warning events in the database.	Number	For complete details of the warning events, use the detailed diagnosis of this measure.
Audit successes	Indicates the total number of audit successes recorded in the events database.	Number	For complete details of the audit success events, use the detailed diagnosis of this measure.
Audit failures	Indicates the total number of audit failures recorded in the events database.	Number	For complete details of the audit failure events, use the detailed diagnosis of this measure.
Others	Indicates the total number of other events in the database.	Number	For complete details of the other events, use the detailed diagnosis of this measure.