Unknown macro: {multi-excerpt-include}
Defining a Watchpoint typically involves:
- Creating a page Watchpoint or an object Watchpoint, and giving it a meaningful name
- Configuring filters to define the segment of traffic that you want to monitor
- Turning on the new Watchpoint
- (Optional) Configuring performance-compliance levels (PCLs) for the Watchpoint
Choose the type of a Watchpoint depending on your needs, for example:
- Page Watchpoint – To monitor the performance and availability for all traffic to your web application (example.com), create a page Watchpoint with a filter to detect only traffic to example.com.
- Object Watchpoint – To monitor the performance and availability of static objects served to your end users from your application, create an object Watchpoint with a filter that can detect objects with the following extensions: .gif, .jpg, .jpeg, .css, .js, and .png.
- Application Watchpoint – To monitor the performance and availability of your web application (or particular parts of the application), create an application Watchpoint.
Note
Each Real User Analyzer instance can bring up to 120 Watchpoints to the system. If you need more than 120 Watchpoints, or if you want to balance the processing load, you can deploy additional Analyzer instances.
Where to go from here
To monitor the Watchpoint for performance, availability, and volume incidents, create incident-detection rules.
Related topics
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks