If a check has multiple steps and monitors multiple pages, you can use Threshold Monitors to set thresholds on any metrics that Rigor collects on individual pages within a user flow. If any of these pages do not meet the set threshold, the whole check will be marked as a failure and alert accordingly.
Thresholds can be set based on timing, resource count and size, and error count.
By default, you will automatically receive an alert for any check that takes longer than 118 seconds. Threshold Monitors enable you to be proactive and implement checks based on thresholds you create to align your site performance with key performance indicators (KPIs) for your specific business needs.
To Set a Threshold Monitor:
- Create or edit a Real Browser Check
- Go to the 'Advanced' tab and add a Threshold Monitor
- Select the metric, the threshold type, and the value you want to set
- Specify what URL of the page you want to monitor
- Avoid adding too many Threshold Monitors to one check. Instead, create a new check for each set of Threshold Monitors
- Make sure that you do not add Threshold Monitors that are mutually exclusive. For example, it's best not to create one that ensures that the page load time is greater than 200 milliseconds and one that ensures it is always less than 100 milliseconds
- Proactively check on how resources are causing page bloat with size & count thresholds
- Set Total errors to 0 to be alerted whenever there is a resource that does not load