Monitor a Web 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.


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.

Application Owners can use this dashboard as their launchpad for an overall summary of the status of their application, and to quickly jump to the main use cases of this application using the quick jump menu.

For example, if your web app is suffering from poor performance, you can easily see the impact from the number of users, their locations, and determine the trend to see if the situation is worse or better than before.

The Monitor Application dashboard for web applications
Field Description

To view the performance data of this web application on specific internet browsers, select them in this menu in the top right hand corner.

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.

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.

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.

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.

Activity Volume

(Managed applications only) Displays the number of times someone performed this activity during the timeframe, thereby adding weight to the impact of this problem. If the same user performs the same activity twice, it counts as two.


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

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.

For more information, see the step below.

When the system calculates the Page Load Time in a web application, it tracks each of the requests and responses to the web server, where typically many of them overlap with each other. Browsers are often highly optimized to speed up the load times.

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).

The infra time for a web application (which consists of network and server times) starts when you click on the link or press enter on the URL, and ends when the browser receives its last response from the server. The remainder is defined as client time. For more details, see the W3C Navigation API.


  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 a web application to monitor.
  4. Step 4 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

    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.

  5. Step 5 To view a summary of the health of the application at a glance, view the summary bar of the dashboard.
    View a summary of the monitored web application
    Field Description

    The User Experience Index (UXI) is a value (0-5) which measures the overall performance and health of an application, based on several inputs: the number of crashes per hour of out the total usage time, the percentage of hang time of out the total usage time, the percentage wait time of out the total usage time. For web applications, it also uses the percentage of web page errors out of all page loads, and the average page load time. These ingredients come together to represent the overall experience of a user.

    Health Score

    The percentage of users whose application is healthy (did not crash) during the dashboard's timeframe. A higher value indicates a healthier application.


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


    (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.

    Page Load Time

    Displays the average time to load a page in seconds for this web application.

    Page Loads

    Displays the total number of times a page was accessed and loaded from this web application.


    (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.

  6. Step 6 To quickly see if any activities for this application are slow and causing widespread disruption, view the activity map in Activity Performance.

    From an activity's position in the map, you can immediately see if many users are impacted, if an activity is performing better or worse than others, and if the recent trend is better or worse than before.

    Quick glance at activities' performance, trend, and popularity

    To read the map, split it into four quadrants, each with its own action item:

    Viewing the Activity Performance map by quadrant

    This map is depicts the relative (not absolute) performance and relative (not absolute) numbers of unique users, so check the values on each axis to ensure the relative differences are significant enough to warrant action.

    Field Description

    Top right quadrant

    This section contains activities which performed as expected, and are more widely used.

    Ideally, all your activities should be in this quadrant, showing that the activities are widely performed, and their performance is as expected.

    Lower right quadrant

    This section contains popular activities used by many people but which performed slower than expected.

    This is a call to action, as it points to wasted productivity by a large percentage of users. We recommend you immediately investigate and resolve why these activities are performing so slowly.

    You can investigate further by drilling down to other dashboards (see later in this step).

    Top left quadrant

    This section contains activities which performed as expected, but were not used often.

    It is worth investigating why so few users are performing these activities.

    Lower left quadrant

    This section contains activities which performed slower than expected, and were not used often.

    Investigate the reason these activities performed so slowly, and why so few users are performing these activities.

    Each activity is listed with its name and an icon indicating its status (color) and trend (direction of the arrow).

    An activity with its status and trend
    Field Description
    Activity name

    The name of the activity as defined in the system.

    If the icons overlap, see the name of the activity by hovering your mouse over the icon.

    Activity status

    The color of the icon represents the status of the score for all instances of this activity.

    Activity performance trend

    The direction of the arrow within the icon represents whether the score for this activity is higher or lower than that from the same timeframe prior to this one.

    You can view the details of an activity or drill down to investigate further by hovering your mouse pointer over that activity.

    View the details of an activity's performance and impact
    Field Description

    Displays the name of the monitored activity within the application.

    Distinct Users

    The number of users who performed this activity at least once, indicating the number of people impacted by this activity's performance issue

    Average Response

    The average of all the response times for this activity during the dashboard's timeframe, measured in seconds.

    Average Remote Display Latency

    (Virtual sessions only) The average time additional delay to performance caused by the extra time required for an action on the client to reach the virtual server to be performed there (remote display latency).

    Current Score

    The activity score which aggregates all the statuses of all the instances of this activity during the current timeframe.

    Previous Score

    The activity score of all the statuses of all the instances of this activity during the same timeframe prior to this one. For example, if the timeframe is 24 hours, Current Score shows the past 24 hours, while Previous Score shows the 24 hours before that.


    The percentage change between the Current Score and the Previous Score.

    You can investigate further on the possible reasons why this activity might be suffering slow performance, by drilling down to any of the following dashboards:

  7. Step 7 To view various indicators by their locations on a geographical map, select the indicator to display in the drop-down menu of the Geographies section.
    View the location associated with different application data
    Field Description
    Overall Score

    Displays a number between 0 and 100 representing the overall health and performance of the application. The color represents is status. This is calculated as the average between the Activity Score and the Health Score.

    Activities 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.

    Activities Volume

    The number of activities in this application performed in the dashboard's timeframe. If the same user performs the same activity twice, it counts as two in this field.

    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.


    The number of times this application crashed during the timeframe.

  8. Step 8 You can limit the scope of this dashboard in the Timeframe field at the top of the screen.

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

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