HTTP Request Type
By default, Rigor checks run as GET requests. If you’d like to change the request type you can select from the dropdown list.
If you selected the HTTP Request Type ‘POST’ you can enter any POST data in this field. This field accepts posts data in XML/JSON format.
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.
Secure Basic Auth
Use this to enable Rigor to talk to sites with basic auth. The username and password is scoped to the domain of the start URL. Credentials won’t be shared with 3rd parties.
Optionally modify the Request Headers for the check. This can be helpful to set a cookie or send over authorization credentials.
Select a network connection setting to simulate various types of connections, such as Mobile LTE or. New checks default to 'Cable' connections.
Success Criteria are conditions for returning the status “success.” We can use settings here to customize Uptime checks to only return status of success if certain text is present or absent, if the server returns a specific HTTP response code, or if the results match a regular expression. If we want to test a redirect we can use the criteria ‘Goes to URL’ and supply the URL where the check should redirect.
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.
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.