Page tree
Skip to end of metadata
Go to start of metadata

To identify application performance as either compliant or non-compliant within a service-level agreement, you can apply page service-level thresholds (page SLTs), rules that specify the acceptable values for page delivery time, using the following latency metrics:

  • End-to-end time (E2E)
  • Page-render time (PRT)
  • Host time

Unlike the system PCLs (which estimate performance of the historical data), page SLTs check every individual page in real time. You can see how many pages pass the performance check in a given period. This is reflected on the dashlets as "X% of pages were too slow."

There are four types of SLTs:

Note

To decide which rule to apply to a particular web page, the system uses the following types of SLTs as an ordered set of overrides (as you can see on the Administration > Thresholds and problem detection > Page service level thresholds (Page SLTs) page of the Real User Analyzer):

  1. If the page name matches a name-based SLT, then that service level is applied to the page.
  2. If the custom field rule that is used to extract the page name matches to a rule-based SLT, then that service level is applied.
  3. If the preceding conditions do not match, the default service level is applied.

Related topics

Defining and managing Watchpoints to group web traffic

Adding an incident detection rule on the Analyzer

Defining system PCLs to measure user experience with an application

Setting up the Collector and Analyzer to report page-render time