Real Browser and Uptime Checks monitor:
- Average Response Time
- Slowest Response Time
- Fastest Response Time
When creating an Uptime or Real Browser Check, visit 'Advanced' settings to set a response time monitor.
If the Real Browser or Uptime check has multiple steps, the response time represents the sum of the Fully Loaded time for each page accessed during the check. So for a single-page Real Browser check, Response Time is the same as Fully Loaded time.
By default, Rigor deems any check that takes longer than 118 seconds to load as a failure and alerts according to the specified notification settings.
You can use a custom Response Time Monitor to define a threshold. If a check’s response time exceeds the time specified in the Response Time Monitor, the check will be marked as a failure and alert accordingly.
Should I set a response time monitor?
Response time monitors affect alerting, making alerts and notifications more aggressive and proactive based on the time thresholds we set. Alerts then affect the Uptime percentage reported in Daily, Weekly, or Monthly performance reports.
- As a best practice, you should only enable custom Response Time monitors if you have a good idea of your baseline Response Time and if you want to be notified any time the site takes longer than that baseline
- For example, if you’re operating around an SLA that your site must load in less than 4 seconds at all times you should consider enabling a custom Response Time monitor of 4000 ms
- If you know your average Response Time is 15 seconds but you don’t need to take action if the site loads slower than 15 seconds, you should not enable a Response Time monitor. You can rely on reports in Rigor to see how often your site’s Response Time is above average