~Performance Navigator: Troubleshoot Tab~

This tab provides a customized interface designed for identifying performance deviations and doing initial triage during a performance problem. In addition to identifying performance deviations, the Troubleshoot tab can be used to obtain a quick overview of application or activity performance, and compare performance among different End Points.

The Troubleshoot tab displays selected performance metrics in table form. These tables are populated after you select a timeframe and other relevant filter parameters. The table views can be then be filtered according to specified criteria (by clicking rows in any of the tables), to show correlations between applications, End Points, and servers.

Selecting Filter Parameters

To generate performance data for the Troubleshoot view grids, you need to select the following filter parameters:

  • Timeframe: You can select a predefined timeframe, or use the Date Navigation toolbar to specify a custom timeframe.

  • Attribute: Select the monitored attribute to be displayed in the grids. One of the following options must be specified:

    • Application Response: Response time for user activities on the selected application

    • Application Latency: Latency attributes for RDP, Citrix, Win32 and HTTP applications

    • Host Resources (WMI): Host information and metrics collected using the Aternity WMI plug-in.

    • Process Resources: Process resources collected using the Aternity Process Resources plug-in. When the system monitors the CPU usage and other device resources of a Windows process (PRC), by default it checks this data hourly. If you want to change this setting as a Power User of Aternity, select the Gear Icon > Settings > Advanced Settings > agent > configuration > overrideConfigurationParam > Process resources > PrcFrequency > value and set the new value in milliseconds.

    • Other Metrics: Custom metrics not covered by the other options.
    • All: All options in the list are included.
  • Application: Select an application from the list. The options displayed in the list vary according to the selected monitored attribute. For example, when Host Resources (WMI) is selected, only WMI parameters appear in the list.

  • Aggregation Level: The level of granularity of displayed data. Levels range from None (raw data is displayed) to Daily (data is aggregated every 24 hours).

For more information about aggregation levels, refer to Aggregation Levels.

The Troubleshoot Grids

The grids display data according to:

  • Activity: Lists all the activities performed during the specified time period, and shows performance metrics of the relevant monitored attribute(s).

  • Host (User): Lists all the End Points on which the selected monitored attributes were measured during the specified timeframe. End Points are identified according to hostname and user name. (User name appears in parentheses, after the hostname.)

  • Destination: Lists all servers that served requests for the activities and hosts that were measured during the specified timeframe. Application servers measure Application Response. CitrixXenApp (ICA) and Terminal Services (RDP) servers measure Application Latency.

All three grids list the following parameters:

Parameter Description Notes


The monitored attribute being measured.

Displayed attributes depend on the option selected from the Attributes drop-down list.


The average measurement.

Units of measurement depend on the attribute being measured. For example, Application Response and Application Latency are measured in seconds, CPU Usage is measured in percent, and Memory is measured in bytes.


The largest or longest measurement.

When Application Response or Application Latency is being measured, this value represents the worst performance.


The performance status (Normal, Critical, etc.).

This parameter allows you to easily identify performance deviations. Deviations can then be correlated with specific activities, hosts, and destinations by filtering the grids and then drilling down to isolate possible causes.


The total number of measurements taken during the specified timeframe.

This value is called the Count or the Volume.

Filtering the Troubleshoot Grids

Data in the Troubleshoot grids can be filtered according to host, activity, or server. When a filter is applied in one table, the other tables are automatically filtered accordingly. For example, when you select a row in the Host table, the system automatically filters the other grids to display only the activities and servers used by the selected End Point.

The Host grid can also be filtered using the Search tool. All End Points relevant to the search term are then displayed in the Host table. The other two tables are automatically filtered to display only the activities and servers relevant to the listed End Point(s).