There are two ways to create a Basic HTTP Uptime Check
- Navigate to Uptime > + New > HTTP
- From the side navigation, click + New > Uptime > HTTP
On the Basic tab:
Name the check
Supply a URL to check
Adjust the check’s frequency and notification settings
With all the basic required fields complete you can click ‘Create’ to start running the check or click on the ‘Advanced’ tab to find additional settings.
By default Rigor will run new Real Browser checks from all available United States locations. Use this setting to disable locations or select additional multiple locations from Rigor’s global monitoring network. For a full list of locations and their IP addresses, see this article.
Notify of location-specific failures
Enable this option to receive failure notifications regardless of location-specific issues. Not sure whether to enable this feature? See this post.
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.
Optionally modify the Request Headers for the check. This can be helpful to set a cookie or send over authorization credentials.
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.
Use escalations to send alerts to new users or groups if an alert has been unacknowledged for a specified amount of time.
We can add multiple escalation emails or repeat escalation emails until a check is ‘back online.’ Read more about setting escalations here.
Specify times when the check should not run. For more information about setting blackout periods, see this article.
Select an existing configuration to use for this check. Read more about configuration templates in this article.