When creating or editing an existing Real Browser check, we will find settings for locations and other customizations on the Advanced tab.
Run checks with the default Firefox user agent string, select from a list of preset user agent strings, or use a custom string. Read more about how to use User Agent strings with the Rigor app here.
Run checks from a default browser size, select from a list of preset viewports for common devices, or set a custom viewport by height and width. Custom viewports are especially helpful for monitoring the performance of mobile or responsive web pages.
Use the Authentication field to add credentials to authenticate with sites that require additional security protocols, especially from within a corporate network. Splunk Synthetic Monitoring now supports a suite of authentication protocols beyond Basic Authentication in the Chrome browser, including NTLM, Kerberos, and Digest.
To use the Authentication field, see How do I include Authentication credentials in Real Browser Checks?
Note: The new Authentication field is only available for Real Browser Checks in Chrome. Firefox Checks still support Basic Authentication.
With this option checked, Rigor will fail a run if an SSL certificate is expired.
Select a network connection setting to simulate various types of connections, such as Mobile LTE or. New checks default to 'Cable' connections.
Response Time Monitor
By default Rigor will count a run as a failure if the response time of the run is greater than 60,000 ms. You may set a custom response time monitor lower than 60,000 ms to make alerting more aggressive. For more ideas about using response time monitors see this article.
For multi-step checks that monitor several pages, you can set lower response time thresholds for specific pages.
You can add DNS override rules to reroute requests from one host to another. This is most helpful when testing an existing production site against page resources loaded from a development site or a specific CDN edge node.
You can preload cookies in the browser before the run starts. Simply add the cookie name and the value into the fields. Any cookies that are set will apply to the domain of the starting URL of the check. We use the public suffix list to determine what the domain is.
Specify files to avoid requesting when running the check. Select from preset options of commonly excluded files or set custom configurations to exclude specific resources. Read more about best practices for excluding files or using exclusions to keep Rigor from affecting your analytics.
Specify custom HTTP headers to send with every request.
Optionally add tags to checks for an organization or to compare checks by tag on a dashboard. Read more about using tags in the Rigor app here.
Select an existing configuration to use for this check. Read more about configuration templates in this article.