Per website, you can configure custom settings that apply specifically to that site.
Verify text on response #
An additional feature of our uptime check, is that it can also look at the source code of the page and match for a particular string.
By default, we just check for an
HTTP/200 code, but you can extend that to match for a pre-defined string. This can be a validation string you place in HTML comments on your site, that you can use as a status indicator.
Minutes downtime before notification #
Our default is to alert you of downtime when a site has been down for 3 minutes. You'll find a detailed explanation in our uptime monitoring documentation.
You can tweak this behaviour to make it alert you sooner or later, by changing the minutes downtime before notification setting.
If you increase this to
10, the site needs to be down for 10 minutes before we alert you. If you lower it to
2, we'll notify you after 2 minutes of downtime.
You can use this setting to tweak particularly important sites, or to lower the false-positive alert rate on sites that have a bad reputation.
Broken links whitelisted urls #
Our crawler checks all pages on your site and will report broken links (timeouts, 404's, 503's, ...). Some pages on your site might be in a known-bad state, and you don't want to report on them.
In the site settings screen, you can whitelist certain URLs that we'll never notify you about.
Custom HTTP headers #
For both our uptime checks or our mixed content & broken links crawling, you can add additional headers to be included on every request. This allows you to include things like HTTP Basic Authentication, add cookies, include a default
There are a few headers you can't overwrite. These are:
In your Site settings page, you can add custom headers as key/value pairs. For instance:
You can also add shared secrets to validate requests coming from Oh Dear on your backend.