Geographic performance-compliance levels

Complex content delivery solutions and geographically dispersed end users make monitoring experience of your web application globally increasingly important.

Geographic location of the end users might affect the service-level thresholds (SLTs). For example, the end-to-end latency of 5,000 ms could be acceptable for end users in China but too slow for end users in New York. To bring the different performance metrics into compliance, set up geographic performance-compliance levels, or Geo PCLs.

You can configure Geo PCLs to characterize end users experience of server or application performance in a given geographic region. Geo PCLs characterize end users experience in a region as satisfied, tolerating, or frustrated.

You can set Geo PCLs for the following metrics:

  • End-to-end time (E2E) — The time it takes for a request to be transmitted across a network from source to destination
  • Page-render time (PRT) — The time it takes to have the web page ready for the end user

Unlike the PCLs that you configure for Watchpoints, Geo PCLs apply only to the geographic zones with which you associate a Watchpoint. You can monitor them by using the Global-Application-Delivery-dashlet and the Global-Application-Delivery-dashlet.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*