Monitor a Desktop Application with Activities Only (Monitor Application)

The Monitor Application dashboard gives Application Owners a quick view on any application (desktop, mobile or web), including its performance, health, and the extent of its usage in your organization, to proactively check if any issues arise, or if any reported issues might be due to that application's deployment.

Note

This dashboard is for applications which only send data on their activity response times. They do not send any discovery data like UXI, because your devices run a legacy version of Aternity Agent (8.x or earlier), or this application was not properly configured in the system. To add discovery data, deploy Agent 9.x on your devices.

The Monitor Application dashboard for desktop applications
Field Description
Summary Bar

View a summary of the health of the application at a glance, and whether it has improved or worsened (see below).

Activity Performance

(Managed applications only) With a quick glance, you can view a graph of the activities which are performing well or poorly, and how widely they are used. For more information see below.

Incidents

(Managed applications only) Displays the number of incidents currently opened automatically by the system on this application's activities. An incident is a call to action, where too many devices in a group have recently started suffering poor performance on the same activity, indicating it is a widespread problem.

You can view the open incidents by hovering over this box and selecting View Incidents to drill down to the Incident List dashboard.

Departments / Business Locations / Regions / Operating Systems / Device Types

Assess the business impact of poor performance by viewing the parts of your organization which are worst hit. Quickly view those with the lowest performance, poorest activity scores, or the heaviest users of applications.

Select a category from the drop-down menu: departments, business locations, regions, device types or operating systems.

Activity Score

(Managed applications only) At a glance, see the trend of the application's performance during the dashboard's timeframe, by viewing the changes in the score (and status) of activities for this application.

Activity Response

(Managed applications only) View the trend of the application's performance during the same timeframe, by viewing changes in the average activity response time (in seconds).

The response times of activities are split into client time ( dark blue), and the combination or union of the server time ( light blue) and the network time ( blue).

Use the actual response times (not scores) to check the performance of chronic (long term) problems. You cannot rely on measurements based on the recent baselines, as those responses would be chronically slow for some time, thereby skewing baselines to make those times look normal.

Geographies

Check if a poor performance is confined to a specific location, by viewing data by locations displayed on a geographical map.

Activity Volume

(Managed applications only) Displays the number of times someone performed an activity in this application, thereby adding impact to its usage. If the same user performs the same activity twice, it counts as two. The icon (if present) represents the overall status, derived from the score.

Crash Rate

The crash rate of an application is the average number of crashes which occurred in that application during an hour of active usage. It is calculated as the total number of crashes divided by the total usage time in hours.

Error Rate

(Web applications only) The web page error rate is the percentage of web page errors (HTTP error 40x or 50x) out of all page loads in web applications. This is one of the elements used when calculating the UXI. For example, if the requested page cannot be found, it issues HTTP error 404. If you are not authorized to view a web page, it returns HTTP error 50x, and so on.

Data Center Locations

(Virtual deployments only) Monitor the application's performance by:

  • Data Center Locations in Aternity lists the locations of any virtual application servers (like Citrix XenApp) and VDI hypervisors (like in VMWare vSphere) which run the application. If the application is deployed both locally and virtually, one of the locations displays as Local.

  • Virtual App Servers displays the name of each virtual application server (like Citrix XenApp) running this application.

For each item, it also displays the number of users, the usage time and wait time, the UXI, and (for managed applications only) the activity score.

Remote Display Latency

Displays the overall latency for virtual sessions (or lag) in seconds for each type of virtualized environment (virtual desktops and virtual applications), gathered from latency measurements taken every minute. It lists the following protocols (if present in your organization):

  • ICA is the protocol used by Citrix XenApp.

  • RDP is the protocol used by Microsoft products like Remote Desktop Connection. It is also increasingly being adopted by newer versions of Citrix XenApp.

  • PCoIP is the protocol used by VMWare's VDI systems.

Procedure

  1. Step 1 Open a browser and log in to Aternity.
  2. Step 2 To access this dashboard:
    • Type the name of the application in the search box in the top bar.

    • Select Main Menu > Monitor > Application.

      Accessing Monitor Application
  3. Step 3 Select the managed application to monitor.
    Select the application to monitor
  4. Step 4 To view a summary of the health of the application at a glance, view the summary bar of the dashboard.
    Note

    This dashboard is for applications which only send data on their activity response times. They do not send any discovery data like UXI, because your devices run a legacy version of Aternity Agent (8.x or earlier), or this application was not properly configured in the system. To add discovery data, deploy Agent 9.x on your devices.

    View essential details of the managed application at a glance in the summary bar
    Field Description
    Overall Score

    Displays a number between 0 and 100 representing the overall health and performance of an application, and its status and color. It is calculated as the average between the activities score and the health score of that application.

    Users

    Displays the number of unique users actively running an application in the foreground, during the dashboard's timeframe.

    Devices

    Displays the number of devices which were actively running an application in the foreground, during the dashboard's timeframe. The same user could access the application on more than one device.

    Latency

    (Virtual sessions only) View the average delay in screen response caused by the remote display latency, displayed in milliseconds.

    You can only see this value if the application is run on a virtual application server or virtual desktop server.

    Total Activities

    (Managed applications only) Displays the number of times someone performed an activity in this application, thereby adding impact to its usage. If the same user performs the same activity twice, it counts as two. The icon (if present) represents the overall status, derived from the score.

    Page Load Time

    (Web applications only) The web page load time is defined as the time required for a web page to load and finish rendering in a browser, from sending a URL request to when the page's events finish loading and it has a status of Completed. This measurement does NOT include the time to load additional page elements which occur after the main page has loaded (like Ajax calls which are measured separately, or iframes which are embedded separate web pages, or bookmarks with # in the URL).

    Page Loads

    (Web applications only) Displays the total number of times a page was accessed and loaded from this web application.

    Incidents

    (Managed applications only) Displays the number of incidents currently opened automatically by the system on this application's activities. An incident is a call to action, where too many devices in a group have recently started suffering poor performance on the same activity, indicating it is a widespread problem.

    You can view the open incidents by hovering over this box and selecting View Incidents to drill down to the Incident List dashboard.

  5. Step 5 You can check the performance of specific activities within the application to uncover exactly which actions have the slowest response times.
    View which activities have the lowest score
    Field Description
    Activity

    Displays the name of the monitored activity within the application.

    Number of Users

    View if poor performance is widespread by seeing the number of unique users actively running the application in the foreground.

    Total Activities

    (Managed applications only) Displays the number of times someone performed an activity in this application, thereby adding impact to its usage. If the same user performs the same activity twice, it counts as two. The icon (if present) represents the overall status, derived from the score.

    Response Time

    (Managed applications only) Displays the response time of the activity. The response times of activities are split into client time ( dark blue), and the combination or union of the server time ( light blue) and the network time ( blue).

    Activity Score

    (Managed applications only) Displays the overall activity score for this application, calculated by condensing all the activity statuses into a single value. Use this for acute (recent) problems in performance.

    Aggregating many end user activities into a single score and status

    For further information you can drill down to:

  6. Step 6 View the sections of your organization worst hit by poor performance of this application.

    Select the category to view, like Departments or Business Locations, and choose the sort order.

    View the department associated with different application data

    View the various parts of your organization impacted by poor application performance. Select a category from the drop-down menu: Departments, Business Locations, Regions, Browsers, Device Types, or Operating Systems

  7. Step 7 To view various indicators by their locations on a geographical map, see the Geographies section.
    Vieww the performance indicators on a specific location
    Field Description
    Crash Rate The crash rate of an application is the average number of crashes which occurred in that application during an hour of active usage. It is calculated as the total number of crashes divided by the total usage time in hours.
    Overall Score

    Displays a value (1-100) which measures the overall performance of a location. It is the average (the mean) between the Activity Score and the Health Score. A higher score indicates a better performance. The status of a score is an Apdex name and color associated with the value of the score:

    Activities Score

    Displays the score of all activities performed in that location.

    Health Score

    Displays a value (1-100) which measures the health of the application in a location, based on the number of crashes per hour out of the total usage time. A higher score indicates a healthier location.

  8. Step 8 (Virtual deployments only) Monitor the application's performance by Data Center Locations or Virtual App Servers.
    Monitor your virtual application performance
    Field Description
    Data Center Locations

    Data Center Locations in Aternity lists the locations of any virtual application servers (like Citrix XenApp) and VDI hypervisors (like in VMWare vSphere) which run the application. If the application is deployed both locally and virtually, one of the locations displays as Local.

    Virtual App Servers

    Virtual App Servers displays the name of each virtual application server (like Citrix XenApp) running this application.

  9. Step 9 View the recent trend of the performance of this application's activities during the dashboard's timeframe.
    Look for spikes or troughs in the graphs, to see if there is a pattern to the performance changes. The graphs have the same horizontal axis, so you can correlate between a longer response time and a lower activity score.
    View the recent trend of activity performance for this application
  10. Step 10 Troubleshoot one activity's response time in a single business location by selecting an entry, to determine the possible cause of a slow response time.
    Isolate the information concerning a single activity, in a single location

    For example, select the activity which has the lowest score in the Activity Performance section to view only the information regarding that activity in all the other sections. If the worst performance is in the Los Angeles location, select this location and check the trend of this activity's performance in the graphs to see when the problem started, if the response time is improving and try to correlate the increase in the response time with other events (for example, with the update of the application, with changes in the network, and so on). You can further investigate this activity by drilling down from the Activity Performance section to the Troubleshoot Activity dashboard.

  11. Step 11 You can limit the display of this dashboard using the menus at the top of the window.
    Select the period of time to display in your dashboard
    Field Description
    Timeframe

    Choose the start time of the data displayed in this dashboard.

    You can access data in this dashboard (retention) going back up to seven days. This dashboard's data refreshes every five minutes.

    Browser

    (Web applications only) Select to display the information regarding Chrome, Internet Explorer, or both.

  12. Step 12 You can jump straight to related dashboards using the quick jump menu at the top of the screen:
    Quickly jump to related dashboards for this application
    Field Description
    Troubleshoot

    Jump to the Troubleshoot Application dashboard for this application.

    Validate Change

    Jump to the Validate Application Change dashboard for this application.

    The system automatically configures the change time to be at midnight just prior to the timeframe of this dashboard.