Overview

About Accops User Experience Manager and Components

Accops User Experience Manager (AUEM) is a suite of multiple components that helps monitor system performance, suggest corrective actions and share details with Accops Reporting Server (ARS) for detailed analysis. AUEM in Accops VDI environment can help:

1. Administrators:
   1. View and analyze server level reports
   2. View and analyze user level reports
   3. Report anomalies
   4. Understand root cause of experience dissatisfaction and improvize
2. End-users:
   1. Notify anomalies
   2. Suggest remediation
   3. View processes and actions to stop processes that are using resources excessively
   4. Improvize system performance using remediation suggested

AUEM Components

AUEM consists of the following components:

AWEM (Accops Windows Event Monitor)

AWEM runs as a Windows service and analyzes the system events based on the user activities. It collects the events data and analyse the recorded data to identify the time span of the different activities. It helps system administrator to identify the issues on user session based on the analysed data sent to the server by the application. AWEM monitors critical system events and sends the event data to ARS or dump event data in an output file

AUPM (Accops User Performance Manager)

AUPM runs as a Windows service and monitors the system performance based on the resource utilization (CPU, RAM, Network) and sends performance data to the ARS based on the threshold values.

Tray agent

Tray agent performs following tasks:

• Notifies the users for the anomalies which are affecting or may affect performance.
• Notifies recommended actions that can be taken on reported anomalies that are found based on the resource utilization.
• Launches Task Manager for end-users to view and manage processes running in user sessions, view memory and CPU utilization.
• View Session network health

• View History of anomalies

  

Task Manager

Task manager provides information about the applications running on the system and their CPU and memory utilization. Task manager can be launched by right clicking the Tray agent.

Task manager has two views Processes and Performance.

1. Processes

   It displays the list of processes running in the user session with their CPU and memory utilization. Users can:

   1. Refresh the list based on the latest data
   2. Close specific process
   3. Sort the table based on the any column

   

2. Performance

   It is the graphical representation of resource utilization by the different processes on the system. Users can:

   1. Refresh the graph based on specific time data
   2. Refresh the graph based on the latest data
   3. View utilization of the specific process
   4. Group the processes based on the following factors.
      • Process ID
      • Process Name
      • Parent Process ID
   5. View detailed graph for
      • CPU Utilization
      • Memory Utilization
      • Process Count

   

Network Latency

Network Latency provides network health information based on the round trip time of a connection. Users can:

1. View graphs for specific time range
2. Refresh the graph

3. View detailed graphs of specific network activity data for:

   • Round trip time
   • Data Send (Kb/Sec)
   • Data Receive (Kb/Sec)
   • Total (Kb/Sec)

   

Notification History

Notification History provides information related to the different user notifications and actions taken by the user on each notification. Users can:

1. Refresh the list to get latest data
2. Filter list based on specific date-time range
3. Sort the table by column

4. Wiew the detail of specific notification

   

Hide/ Unhide Notifications

Users can perform following actions from Tray manager for notifications:

• Hide Notification: Use this option provided in the tray manager to hide all the notifications for specific time duration.

  

• Enable Notification Use this option provided in tray manager to unhide the notification.

  

Anomalies

Any kind of excessive utilization of resources - Memory, CPU, Number of applications; or weak network in session, which can affect user experience on system is termed as anomaly.

AUPM detects the anomalies and notify users to take corrective actions. It also reports such incidents to ARS for auditing and analysis purpose. Following evaluations are done for identifying the anomalies on system:

1. Processes Count
2. CPU utilization by processes
3. Memory utilization by processes
4. Session connection network health

Process Count

AUPM will consider count of processes running as an anomaly when it reaches the threshold limit. Appropriate notification with corrective actions will be shown to the user. In following cases, AUPM will notify anomaly:

1. All process: Total number of user processes running in a user session is more than the defined threshold limit.

2. All process with browser: Browser processes in a user session is more than the threshold limit for browser processes.

3. Same process instance: Count of multiple instances of a process running in a user session is more than the threshold limit.

4. Child process instance: Count of child instances of a process running in user session is more than the threshold limit.

In all of the above cases, AUPM will notify user with following corrective action suggestions:

• Check the details of processes running in the session.
• Ignore notification for specific time: This is used to show the next notification to user if anomaly still exist on system.
• Close process instances.
• Logout from the system.

Resource consumption by User Process

If the CPU or Memory utilization for a process is more than the threshold limit then the user is prompted with warning. Different threshold for CPU and memory can be set to define anomaly level.

Suggested Corrective Actions:

• Check the details of all those processes that have reached the threshold limit.
• Change the ignore time of the notification. This is used to show the next notification to user if anomaly still exist on system.
• Close instances

Collective Resource Consumption in User Session

This is used to detect user processes CPU or Memory utilization is more than the threshold limit then prompt warning to user.

1. CPU Utilization
   If the CPU utilization of the user processes is more than the threshold limit, then the user is prompted with warning. To resolve the anomaly user can take following actions:

   • Change the ignore time of the notification - This is used to show the next notification to user if anomaly still exist on system.
   • Logout from the system.
   • Check the detail of processes running in the session.

2. Memory Utilization
   If Memory utilization of the user processes is more than the threshold limit then the user is prompted with warning. To resolve the anomaly user can take following actions:

   • Change the ignore time of the notification - This is used to show the next notification to user if anomaly still exist on system.
   • Logout from the system.
   • Check the detail of processes running in the session.

Identical User Process Consumption

If for the multiple instances of the same process (detected on the process name) CPU or Memory utilization is more than the threshold limit then the user is prompted with warning. To resolve the anomaly user can: - Change the ignore time of the notification. This is used to show the next notification to user if anomaly still exist on system. - Close instances - Check the detail of processes which reached the threshold limit.

Collective system process consumption

This is used to detect system processes CPU or Memory utilization is more than the threshold limit, then prompt warning to user.

1. CPU Utilization: If CPU utilization of the system processes is more than the threshold limit, then prompt warning to user, for resolving the anomaly user can take following actions

   • Change the ignore time of the notification.
     • This is used to show the next notification to user if anomaly still exist on system.
   • Logout from the system.
   • Check the detail of processes running in the session.

2. Memory Utilization: If Memory utilization of the system processes is more than the threshold limit then prompt warning to user, for resolving the anomaly user can take following actions

   • Change the ignore time of the notification.
     • This is used to show the next notification to user if anomaly still exist on system.
   • Logout from the system.
   • Check the detail of processes running in the session.

Remote Session Network Bandwidth

Remote session network bandwidth evaluation type is used to check the session connection health and if latency is reached the threshold value then prompt warning to user.