AppC Operations Test

If a user complains that his/her transactions with the App Controller are failing, administrators may first want to know which steps of the user interactions are failing often. The AppC Operations test provides administrators with this useful information. This test scans the AppController Syslog file for the type of operations users performed on AppController. 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, the test highlights those operations that failed very often and caused the user experience with the AppController to suffer.

For this test to run and report metrics, the AppController should be configured to create a Syslog file in a remote Syslog server, where the details and status of all user interactions with the AppController will be logged. The steps for achieving the same are discussed in the below section.

Configuring the Syslog server

To configure the Syslog server where this Syslog file should be created, do the following:

  1. Connect to the AppController management console using the URL: https://<IP_address_of_AppController>:<AppController_port>
  2. Login to the AppController as an administrator.
  3. Figure 1 will then appear. Click the Settings option in Figure 1.

    syslog1

    Figure 1 : The AppController management console

  4. Next, scroll down the System Configuration panel of Figure 2 until the Syslog option becomes visible. Then, click the Syslog option. This will bring up a Syslog page in the right panel, where you can configure a remote Syslog server and enable Syslog file creation on the server.

    syslog3

    Figure 2 : Configuring the Syslog server where the Syslog file is to be created

  5. To configure a new Syslog server, enter the IP address of the Syslog server in the Server text box of Figure 2.
  6. Enter the Port at which the Syslog server listens.
  7. Let the Facility remain at 2.
  8. Then, indicate what details should be logged in the Syslog file that will be created in the specified Syslog server. For the eG tests to work, at least the Audit check box should be selected. 
  9. Click the Save button in Figure 2 to register the changes.

Target of the test : Citrix AppController

Agent deploying the test : A remote agent

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

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.

Host

The IP address of the host for which the test is being configured.

Port

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

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 AppController will be creating this file, refer to Configuring the Syslog server.

SSL

Indicate whether/not AppController is SSL-enabled. By default, this flag is set to Yes.

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.

The detailed diagnosis of the Successful operations measure reveals 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.

DDsuccessfuloperations

Figure 3 : The detailed diagnosis of the Successful operations measure