A Watchpoint is a configurable subset of web traffic, such as traffic associated with an application or traffic coming from a certain geographic area.
Use Watchpoints to filter web traffic for the monitoring purposes. For example, you can set up the performance dashlets to show traffic from a certain Watchpoint.
By default, the system includes a number of typical filters that you can select to create Watchpoints, for example:
- Traffic to a particular web application
- Traffic from a particular group of end users
- Traffic from a particular geographic region
- Traffic from a particular client platform
You can define Watchpoints based on these default filters, but also you can build sophisticated filter queries using Expression Builder.
You can monitor the Watchpoints on the Watchpoint Summary page of a Real User Analyzer.
Note
You have a limited number of Watchpoints that you can use at a time. Read more in Licensing and archiving Watchpoints.
Defining Watchpoints
To perform this procedure, you must have Operator-level access, or higher, or have tenant Application Owner-level access.
Defining a Watchpoint typically involves:
- Creating a page Watchpoint or an object Watchpoint
- 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 Watchpoint type that satisfies your requirements.
- 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
Monitoring traffic, availability, and performance in real time from a Watchpoint
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks