In order to add a new test you should first login to your account, then navigate to the tests section of the sidebar, from here click the ‘new test’ option in order to begin the creation process.
The first option is “Test Type”, which should be Http/Https by default for a website, keep this option and continue.
The second field is “Test Name”, here you should enter the desired title for the test – as you would like it to appear in the control panel and reports.
The next field “Test URL” should be populated with your web address (i.e http://Statuscake.com), optionally you can enter an IP address here instead.
The next field “Basic Auth” is optional and only needs to be used if the website you are monitoring requires user authorization.
In the contact groups field that comes next, you can select contact groups to be notified regarding this test, for more information on contact groups please click here.
Next you will see the “Test Locations” selection, here you can select the regions and locations that will carry out the testing on a paid plan. Be sure to select at least three locations if you are using specific locations – this will mean your tests always come from these locations, and is needed to support confirmation server checks.
In the next section you can enable SSL Certificate monitoring by turning on “SSL Scanner”.
Next we have “Alert Delay Rate” another important setting which indicates how long a server should be checked as being unresponsive before we notify you, useful if you don’t want to know about short periods of down time, a good example being server restarts.
The next option “Confirmation Servers” sets how many servers you would like to confirm an issue before we notify you, having more confirmation servers can mean longer waits before notifications.
You can use the “User Agent” field to set a custom user agent to be sent with the test – this field is overridden if you have data in the custom headers box.
The “String Match” field can be used to be alerted if a string is found/not found on the page being tested, and the “Enable headers” option will also check the headers of the document for your string,
In the next section you will choose whether your test should Follow Redirects and store cookies. And you can also define an expected final location for the test to ensure that the right page is always reached. Custom Headers for the test are defined next – if required, these should always be in valid JSON format.
Moving on you should now see the “Status Codes” section, this is a list of status codes that if detected on your server will result in an error and thus an alert, the list is already preloaded with the status codes you would need for most cases.
Scroll down to the next important section that requires your attention “Crawl Timeout”, here you should input the number of seconds you want our servers to wait for the first byte before judging that the server that you are monitoring has gone down, by default this is set to 40 seconds.
You have the option to add a preconfigured “Maintenance Window” in this section, simply click to add one into the field. This will prevent you being notified of downtime that you have planned for.
The next field “tags” should include keywords or identifiers that will allow you to filter your test once it was done, for example – tests running on servers in France might have the tag FR.
After you are happy with all of these options, simply scroll down and click submit. The test will then be created and will be available for viewing within the control panel.