Defining page SLTs to measure application performance compliance on the Analyzer

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:

• Page SLT by Specific Page Name — Use it when you know the exact page name.
• Page SLTs by Specific Watchpoint — The system creates this threshold when you define a Watchpoint.
• Page SLT by Page Name Extraction Rule — Use it when the page name is specified by the result of a page name extraction rule.
• Default Catch-All — Use it for all the pages that have no SLT specified.

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