View a Change on the Performance of Multiple Applications (Validate Infrastructure Change)

The Validate Infrastructure Change dashboard compares the performance of several managed applications before and after you make an infrastructure change, or some other change which impacts several applications. The changes could be limited to a single location or across multiple locations.

For example, if you change a setting in the firewall, or change router settings in a site, you can view the performance impact of those changes across a range of applications in a site, or across multiple sites.

The Validate Infrastructure dashboard

This dashboard focuses on changes across several applications. To compare the performance of a single application before and after a change, see Validate a Change on a Single Application's Performance (Validate Application Change).

Procedure

  1. Step 1 Open a browser and sign in to Aternity.
  2. Step 2 Select Main Menu > Validate > Infrastructure Change.
    Accessing Validate Infrastructure Changes
  3. Step 3 Select the scope of data displayed in the Validate Infrastructure Changes dashboard.
    Defining the scope of view in the Validate Infrastructure Changes dashboard
    Field Description
    Does the change in infrastructure affect some or all locations?

    Select whether this dashboard shows a single business location or multiple locations.

    Select the business location

    If you specify above that the change is restricted to a specific location, select it.

    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, Aternity does not display gathered data from the transition phase.

  4. Step 4 To compare the performance of multiple applications before and after a change, view the Applications section to see if performance improved or worsened as a result of the change.

    This section compares the average response times or percent change of each managed application before and after the change, sorted by those which performed worst as a result of the change.

    Comparing average response times for each monitored application

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

    Field Description
    Before

    Displays the average response time for all monitored activities of this application before the change took place. This value is also displayed as a vertical line.

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

    After

    Displays the average response time for all activities in this application 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.

  5. Step 5 To view more details on a single application in this dashboard and to further investigate it in other dashboards, hover over its horizontal bar.
    Viewing details of the impact of the change on a single activity
    Field Description
    Application (only in dashboards with multiple applications)

    Displays the name of the monitored application, as it appears throughout the system. You can customize it when you add it as a managed application.

    Before Response Time

    The average activity response times for this application, in seconds, both before and after the change.

    After Response Time
    % Change

    Displays the percentage change of the response times between before and after the change. If the response time increased (worsened), it is a negative number.

    Activities Before

    Displays the total number of activities for this application before and after the change during the timeframe.

    Activities After
    Errors Before

    Displays the number of activities for this application which did not complete successfully before and after the change. For example, if the email program could not find the new server, all activities associated with fetching and opening mails would be classed as errors.

    Errors After

    A negative change signals a worsening in performance. To troubleshoot the problem, you can drill-down to:

  6. Step 6 To view the response times for each application as they change over time (not a single average) during the comparison period, view the Trends section on the right side of the dashboard.

    The Trends section displays a separate graph for each application, showing average response times (in seconds) rising and falling during the comparison period. The system ignores data gathered during the transition itself.

    For example, if the response time of Microsoft OneNote improved (decreased) sometime before the change, it means your change did not cause the improvement. The change was obviously beneficial for BranchPortal whose response time decreased after the change.

    Viewing each application's performance changes over the comparison period
    Field Description
    Response Time The vertical axis, and the graph line in purple, indicate the changes in the average response times for all monitored devices over the comparison period.
    Average Response for Period The graph line in dark gray, indicates the average value (always flat) of the activity-response times across that comparison period; either before or after the transition. This is the same value listed in the Applications > 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 see if the infrastructure change impacted individual locations, servers, device types or browsers, compare the breakdown of the normalized percentage change in performance across your organization.

    By default, the list is sorted by those worst affected by the change.

    For example, if you consider replacing the browser for your accounting web application, you have to compare the application's performance in different browsers, so select Browsers in the drop-down list of the section. If you make a change to the SharePoint server cluster, select Servers to view the impact of that change. Compare the performance of people connecting to this cluster versus users connecting to other clusters.

    View impact of a change across locations
    Field Description
    Business Locations

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

    Servers

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

    Device Types

    Displays the types of devices on which the application runs.

    Versions

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

    Browsers

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

    Browser Versions

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

  8. Step 8 To view how the change impacted application performance in a single location, select a single location in the Locations section, then view the applications in the Applications and Trends sections.
    View impact of a change in a single location

    You can similarly view the impact of the change on a single application by selecting that application and viewing the other sections of the dashboard. For a more detailed view of the impact on each activity of a single application, see Validate a Change on a Single Application's Performance (Validate Application Change).

  9. Step 9 You can limit the display of this dashboard using the menus at the top of the window.
    Changing the data displayed in the Validate Infrastructure 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, Aternity 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.

    Application

    Select a monitored application to display its activities in this dashboard.