How to set up website monitoring and alerts in Spot Downtime

A step-by-step guide to your first monitor: add a website, check that the page really loaded with a keyword, and get alerted in Slack, by email or by text when it goes down.

· 5 min read · By the Spot Downtime team

This is the first guide in a short series on getting the most out of Spot Downtime. By the end of it you'll have a website monitor that checks your site every few minutes, an extra check that the page really rendered, and an alert channel that tells you the moment it breaks. It takes about five minutes.

Step 1: add a website monitor

  1. Open Monitors in the app and click Add monitor.
  2. Choose Website.
  3. Paste the URL you want to watch, such as https://example.com. Pick the page that matters most: often the home page, but a login or checkout page catches more problems.
  4. Give it a Name if you like. It defaults to the address.
  5. Choose how often to Check every. The Free plan checks every 5 minutes, Starter every minute, Pro every 30 seconds.
  6. Click Add monitor. The first check runs within a few seconds.
A website monitor for a checkout page, with a keyword check.

Each check sends a GET request. Any status from 200 to 399 that arrives within 10 seconds counts as up; anything else, a timeout or a connection error counts as down.

Step 2: check the page really loaded

A server can answer 200 OK with a blank page, a framework error screen or a “We'll be right back” message. To catch that, fill in Page must contain with a piece of text that only appears when the page works:

  • On a shop: Add to cart
  • On a login page: Forgot password
  • On a marketing site: a phrase from the footer, which renders last

If the text is missing, the monitor counts as down. The match isn't case-sensitive. Avoid text that changes often, like prices or dates, or you'll get false alarms after every content edit.

If your firewall blocks the checks

Cloudflare, a WAF or bot protection may block monitoring traffic. Either allow our check addresses, or add a secret header under Headers (for example X-Uptime-Check: a-long-random-value) and let requests with that header through. The allowlist docs walk through both.

Step 3: choose where to check from

Checks run from California, Amsterdam and Singapore. On every plan, a failed check is retried after 2 seconds and confirmed from the other regions before anyone is alerted, so a single network blip doesn't wake you up.

On Starter and Pro you can pick regions in Check from: the one nearest your users, or several to check from each of them every interval. With several, you're alerted when most of them can't reach the site.

One failed check never alerts on its own: it's retried, then confirmed from the other regions.

Step 4: add an alert channel

A monitor without an alert channel only shows its status in the app. To be told when it changes:

  1. Open Alerts and click Add channel.
  2. Choose where alerts go: Slack, Discord, Microsoft Teams, Google Chat, Telegram, PagerDuty, email, SMS, a voice call, WhatsApp, a webhook and more.
  3. Paste the address or key. For SMS and calls, verify the number with the texted code.
  4. Click Send test and check it arrives.

Every channel in the workspace hears about every monitor. You get one alert when a monitor goes down and one when it recovers, with how long it was down; never a stream of repeats while it stays down.

One alert when it goes down, one when it recovers.

Use two channels for anything important

Chat channels are great during the day and easy to miss at 3 a.m. Pair Slack or Teams with something that interrupts you, like SMS, a voice call or PagerDuty. Every plan includes some SMS and call credits each month. See SMS uptime alerts for when they're worth it.

Step 5: make sure it works

Open the monitor. You'll see its status, recent checks, uptime and a response time chart. To see a real down alert end to end, add a second monitor pointed at a URL that doesn't exist on your site with Page must contain set to some text that isn't there. Within a check or two it goes down and your channels get the alert. Delete it afterwards.

What to monitor next

  • Your API, with checks on the JSON it returns, not only the status code.
  • The cron jobs and workers that keep things running behind the scenes.
  • The third-party services you depend on, like your payment provider or cloud region.

The rest of this series covers each of these:

Don't have an account yet? Create one for free; the Free plan includes 20 monitors.

Get new guides by email

Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.

Unsubscribe from any email with one click. See our privacy policy.

Keep reading