Validate a Change on a Single Application's Performance (Validate Application Change)

The Validate Application Change dashboard compares the performance of a single managed application's activities before and after you make a change.

For example, if you change a setting in your enterprise application (like your custom banking application), you can validate the effect of the change on end user performance. Similarly, in Microsoft Outlook, if you increase the RAM of your Microsoft Exchange Server, or change its hard disk configuration, you can check if devices experience faster response times when opening a new mail. Or if you update Microsoft Outlook clients, you may want to confirm that launch times are not slower than before.

Validating a change to a single application

This dashboard focuses on changes in a single application. To compare the performance of several applications before and after a change, see View a Change on the Performance of Multiple Applications (Validate Infrastructure Change).

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
Monitor

Jump to the Monitor Application dashboard for this application.

Troubleshoot

Jump to the Troubleshoot Application dashboard for this application.

Commonalities Analysis

Jump to the Commonalities Analysis dashboard for this application.

Procedure

  1. Step 1 Open a browser and log in to Aternity.
  2. Step 2 Select Main Menu > Validate > Application Change.
    Accessing Validate Application Changes
  3. Step 3 Select the scope of data displayed in the Validate Application Change dashboard.
    Defining the scope of view in the Validate Application Change dashboard
    Field Description
    Select the application

    Choose the name of the application from the list of monitored applications, whose performance you want to compare.

    If your application is not listed, ask your Power User of Aternity or Administrator of Aternity to add the application. For more information, see View the List of Managed Applications.

    Does the application impact more than one activity?

    Select No to narrow the view to a single activity of the application. Select Yes to view all monitored activities in this application.

    Select the date of the change

    Select the date of the start of the change to the application. This is the date of the comparison. The dashboard displays several days before and after this date.

    Select the duration of the change (days)

    If the change took more than one day, enter the number of days required for the transition. For the purposes of comparison, the system does not display gathered data from the transition phase.

  4. Step 4 To view the performance of a single application, view the Response Time in the Activities section.

    This section compares the average response times for every monitored user activity in this application before and after the change.

    Comparing average response times per activity
    Field Description
    Activity

    Displays the name of the monitored activity within the application.

    Before

    The average response time for this activity before the change took place. This value is also displayed as a vertical line.

    It represents the average of the response times of all the instances of this activity, for the period before the change which impacted the application.

    You can change the comparison period at the top of the page, in the Days to Compare field.

    After

    The average response time for this activity after the change took place. This value is also displayed as a green, gray, or red bar:

    • A green bar represents at least a 10% improvement in response times (faster, lower number of seconds).

    • A red bar represents at least a 10% worsening in response times (slower, higher number of seconds).

    • A gray bar represents less than 10% change either way in response times.

    Note

    If you upgraded your application, verify that all your existing activity monitors still function in the upgraded version of the application.

    To do this, check that the volumes for each user activity of this application before and after the change have not dropped significantly since the upgrade. If you receive zero reports from one location or all locations, ask your Administrator of Aternity to update the monitored application in the system. You can do this in the Activities section, by hovering over a measurement and viewing the Volume Before and Volume After readings.

    Checking that an activity is still monitored after an upgrade

    For more information on a particular activity, drill down to the Troubleshoot Activity dashboard (see Troubleshoot a Single Activity (Troubleshoot Activity)).

  5. Step 5 You can also view performance data changes as a normalized percentage change. In the Activities section, select Percentage Change from the drop-down menu.
    Viewing percentage change in performance per activity

    For example, if you change the network infrastructure and expect a 2 second improvement in response times, the percentage improvement would vary massively depending on the previous measurement. It would be 66% if it used to be 3 seconds, or 16% if it used to be 12 seconds. So in this case, you may prefer to see the absolute value.In contrast, adding RAM would yield a proportional improvement across the board, and may therefore be better to see the percentage improvement.

  6. Step 6 To view the recent history of an application's performance before and after the change you made, view the Trends section on the right hand side of the dashboard.

    It shows a graph for each activity in this application, displaying the response times (in seconds) rise and fall during the comparison period. The system ignores data gathered during the transition itself. For example, if you see a significantly higher line before the change, and a lower line after the change, you can conclude an increase in efficiency for that activity. If your change was aimed at improving performance of a specific activity at peak hours, you can view those hours before and after the change on the trend line to validate if your change did indeed reduce response times.

    Viewing detailed changes in activity-response times over the comparison period
    Field Description
    Response Time The graph line in purple, indicating the changes of the average response times for all monitored devices over the comparison period.
    Average Response for Period The graph line in dark gray, indicating the average activity-response times across that comparison period; either before or after the transition. This is the same value listed in the Activities > Response Times section.
    Change Start Indicates the start of the upgrade or change which impacted the application. The system ignores activity-response times during the transition period.
    Change Complete Indicates the end of the upgrade or change which impacted the application.
  7. Step 7 To view the changes in an application performance in the various locations in your organization, according to their associated servers, versions, or types of devices, view the bottom left side section of the dashboard.
    Viewing percentage change in performance by server
    Field Description
    Business Locations

    Displays the name of the locations where your application is used.

    For example, if some users still complain of slow performance after your change, you can isolate whether the slow results are restricted to one location or are spread across your organization. Use Locations to compare the performance before and after a change for each location.

    Servers

    Displays the host names of the servers where the application runs.

    For example, if you updated the version of the client side of an application across the organization, but some users still complain of slow performance, you can isolate whether the slow results are restricted to one server or if it is spread across all servers.

    Device Types

    Displays the types of devices on which the application runs.

    For example, if you updated a server setting, but some users still complain of slow performance, you can isolate whether the slow results are restricted to just laptops, or if it is spread across all monitored devices.

    Versions

    Displays the version of the application whose performance is checked before and after the change.

    For example, you can see how your change influenced the response time of Microsoft Outlook 16.0.6741.2056 compared to the response time of Microsoft Outlook 15.0.4849.1000.

    Browsers

    (Web applications only) Displays the type of web browser housing the application.

    For example, you can see how your faster network card influenced the performance of Gmail in Internet Explorer, compared to Chrome or Firefox.

    Browser Versions

    (Web applications only) Displays the version of the web browser housing the web application.

    For example, after you upgrade to Internet Explorer 11 on a few devices, you want to compare the performance of Gmail in Internet Explorer 10 and Internet Explorer 11.

  8. Step 8 Hover your mouse pointer over the horizontal bars, to view more details like the number of activities performed at each location, whether there is a change in the errors, and so on.
    View details of the performance before and after the change, in the tooltip window
    Field Description
    Business Location

    Displays the name of the location whose performance you are comparing.

    Before Response Timeand After Response Time

    Displays the average response time of the application, for the selected location/server/device type/application version/browser, before and after the change.

    Activities Before and Activities After

    Displays the number of activities reported in that location before and after the change. This should not be significantly different. If it is, check your activity definitions are still valid for the new version of the application.

    Errors Before and Errors After

    Displays the number of times an activity started but did not complete. Both these fields should be close to or at zero. If you notice an increase in this number before and after the change, check that your activity definitions are still valid for the new version of the application.

    % Change

    Displays the percentage change in the average performance of this application in this location.

  9. Step 9 To view the performance of a single activity, select that activity and then view its associated locations, servers, device types, and trends.
    Viewing the associated details of the impact on a single activity

    For example, if you want to see the influence of the RAM you added to all your laptops on the Microsoft Outlook launch time, select Launch in the Microsoft Outlook Activities section, and check if its value on the laptops improved (decreased) by selecting Device Types > Laptop in the Device Types section.

  10. Step 10 You can limit the display of this dashboard using the menus at the top of the window.

    You can change the application you want to compare, the date of the change you made, and the number of days to compare on either side of the change.

    Changing the time frame of the dashboard
    Field Description
    Change Time

    Select the start date of the change to the application. This is the date of the comparison. The dashboard displays several days before and after this date.

    Transition Days

    If the change took more than one day, enter the number of days required for the transition. For the purposes of comparison, the system does not display gathered data from the transition phase.

    Days to Compare

    Enter the number of days to display on either side of the change.

    Activity

    Limits the display of the dashboard to one or more specific activities.