Key Task: Validate an Infrastructure Change

You can validate a change which impacts many applications in your organization using Aternity. If you made a deeper change, for example, like changing your firewall configuration, or some other infrastructure change, you can assess the impact on the end user performance of multiple applications across the board.

There are several ways to do this.

To... Do this...

To validate that your infrastructure change improved the performance of all monitored applications, or alternatively to validate that the change did not worsen their performance

Use the Validate Infrastructure Change dashboard.

To check the network health after your infrastructure change, check the time it takes for an application to send and receive a response from the server.

In the Troubleshoot Activity dashboard, check the Trends section to see the changes over the period of your change, and hover your mouse pointer over a response time to view the Client Time, Backend Time, In Traffic and Out Traffic.

To view if there was a change in errors or crashes of this application resulting from the change

Use the Device Health dashboard.

View the Trends section to see an overview of the number of errors, crashes, and other health events during the comparison period. To narrow the data to a specific application and date range:

  • Set the dates to display a sufficient time before and after the change.

  • Select the type of issues you want to display in the Health Events section (like system errors, or application-specific crashes).

  • To display only the events associated with the process name, use the Components section.

To view the impact of changes to your virtual application environment

Check the application performance in the same way as you would for a non-virtualized application in the Validate Infrastructure Change dashboard.

To view the impact of changes in your virtual desktop (VDI) deployment

Use the Desktop Health dashboard to check the health of the virtual machine in the VDI. You can see the number of occurrences of system crashes (like BSODs), application crashes, changes in resource consumption for CPUs, and look for changes in the processes using the highest resources.