A monitoring point can become overloaded if there are too many web path tests running simultaneously. Under heavy use, web path test execution can be delayed. When a monitoring point becomes overloaded, web path tests will be dropped. You can view the monitoring point load at any time. When there are heavy load and overload conditions, messages indicating this can also be seen on the Test Timeline page. The following table shows the various heavy load conditions, how the conditions are indicated, and what to do about them.
|Condition||Indicator(s)||Message text||Action(s) to take|
|Heavily used monitoring point||Message||The Monitoring Point is close to being overloaded with web transactions.||Consider reducing web path test load.|
|Heavily used monitoring point, transactions delayed||Message,||The most recent monitoring results were delayed.||Consider reducing web path test load.|
|Overloaded monitoring point||Message, grey chart||The Monitoring Point is overloaded with web transactions.||Reduce web path test load.|
Determining monitoring point load
To determine how heavily the monitoring point is loaded:
- Navigate to Experience > Web Paths.
- Find the web path you are interested in.
- Click the web path you want to view.
- The Test Timeline page appears.
- In the Monitoring Point Details pane (right side of the page), the Load field shows the monitoring point load.
Reducing web path test load
To reduce the web path test load, try one or more of the following:
- Reduce the number of web applications that you are monitoring from the overloaded monitoring point.
- Reduce the number of workflows configured in a web app group.
- Reduce the number of milestones configured within one or more workflows.
- Increase one or more of your web path test intervals.