Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Web Performance Monitor (WPM) > WPM - Knowledgebase Articles > Inconsistent WPM transaction results between locations

Inconsistent WPM transaction results between locations

Updated December 6th, 2016

Overview

This article describes the behaviour when two different WPM locations have differing playback times for the same transaction. 

 

 

Environment

  • WPM version 2.2.1
  • Orion version 2016.1.5300

 

Cause 

Having multiple locations is allowed for monitoring from separate discrete locations. It is expected the playback times of one Transaction would have different playback times when monitored from different locations.

 

Resolution

 

Review each Transaction and identify the steps which differ in playback times.

In the WPM Web Console browse to the steps and review the TCP Waterfall charts. These charts will visually display a breakdown of the step's behaviour which can be compared across the locations. The difference in the charts will indicate the cause of the difference between the same Transaction in the different locations. 

 

Last modified

Tags

Classifications

Public