XM Console Operations Test

In large environments multiple XenMobile administrators may be present to overlook the user interaction with the XenMobile. In such environments, it may be difficult for an administrator to keep a constant vigil on the operations performed by other administrators. The XM Console Operations test provides administrators with the knowledge of all the operations performed by all the administrators in the target XenMobile environment. This test scans the XenMobile Syslog file for the type of operations administrators performed on the XenMobile. For every operation so discovered, this test then reports the number of times that operation succeeded and the number of times it failed. This way, administrators can figure out the exact reason for those operations that failed very often.

For this test to run and report metrics, the XenMobile server should be configured to create a Syslog file in a remote Syslog server, where the details and status of all user interactions with the XenMobile server will be logged. To know how to configure a remote Syslog server for the use of the XenMobile server, refer to 1 of this document.

Target of the test : A Citrix XenMobile

Agent deploying the test : A remote agent deployed on the Syslog server

Outputs of the test : One set of results for every operation users performed on XenMobile.

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

The port at which the specified host listens. By default, this is 4443.

Log File Path

This test reports metrics by parsing a Syslog file. Specify the full path to the Syslog file here. To know how to configure the Syslog server where the XenMobile will be creating this file, refer to XM Console Operations Test.

Search String

By default, the Syslog file may contain information relating to a number of servers that are inter linked with the target Xenmobile. In order to obtain the metrics of the target XenMobile alone, specify the hostname or the IP address of the target XenMobile server for which the logs are to be read from the syslog file, in the Search String text box. Using this search string the information in the Syslog file may be parsed and metrics may be collected.

Search String Index

Here, specify the cursor position after which the eG agent should search for the specified Search String (or the position upto which the eG agent should ignore while searching for the specified Search String) in the syslog file. For example, if the specified search string appears in the syslog file at the 17th position, then you may need to specify the Search String Index as 16.

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 suite 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

Successful operations

Indicates the number of times this operation succeeded.

Number

A high value is desired for this measure.

Use the detailed diagnosis of this measure to view the names of the users who succeeded in performing an operation, when they performed the operation, and the client/receiver each user used for this purpose.

Failed operations

Indicates the number of times this operation failed.

Number

A very low value is desired for this measure.

Use the detailed diagnosis of this measure to view the names of the users who failed to perform a particular operation, when they tried to perform that operation, and the client/receiver each user used for this purpose.