Skip to content
HonkWatch
PricingLocationsHonk RadarHelpAPI Log inGet started
All help topics

Getting started

  • Getting started
  • How checks work

Monitors

  • Which monitor to use
  • Website monitor
  • API monitor
  • Keyword monitor
  • Ping monitor
  • Port monitors (TCP and UDP)
  • DNS monitor
  • SSL certificate monitor
  • Domain expiry monitor
  • Third-party services
  • Page load monitor
  • Heartbeat monitor (cron jobs)
  • Maintenance windows
  • Incidents

Alerts

  • Setting up alerts
  • Email alerts
  • Slack
  • Microsoft Teams
  • Discord
  • Telegram
  • PagerDuty
  • ntfy
  • Webhooks
  • Zapier

Phone and desktop app

  • The phone and desktop app
  • App alerts not arriving

Status pages

  • Status pages
  • Status page on your own domain

Team and account

  • Team members
  • Plans and limits
  • API keys and the API
  • Your account

Troubleshooting

  • A monitor says down but my site works
  • I did not get an alert
  • Allowing our checks through a firewall
  • Questions and answers

Help / Alerts

Setting up alerts

Alerts tell you when a monitor goes down, comes back, gets slow or has a certificate about to run out. You choose where they go by adding alert channels on the Alerts page.

How channels work

A channel is one place an alert goes: an email address, a Slack channel, a webhook address and so on. Each channel applies to all the monitors in your account. You do not pick channels per monitor.

When you add a channel, you tick the events it should get:

TickWhat it sends
DownA monitor has been confirmed down. This also covers a DNS monitor whose answer changed, when Alert when the answer changes is ticked on that monitor (it is by default). DNS changes are not sent to PagerDuty.
Back upA monitor that was down is working again. The message says how long it was down and what the cause was.
Certificate expiringA certificate has fewer days left than the number set on the monitor (14 unless you change it). Website, keyword and SSL certificate monitors have this setting.
SlowA monitor answered slower than the limit you set on it. Only monitors with a limit in Alert when slower than (ms, optional) send this.

All four are ticked when you open the form. Untick the ones a channel should not get.

Add a channel

  1. Open Alerts and press Add alert channel, or scroll down to Add a channel.
  2. Under Where should alerts go?, choose the kind of channel. The hint under Send to changes to say what to enter.
  3. Fill in Send to. For an email channel that is the address. For most others it is a web address you copy from the other service.
  4. Give it a name in Label (optional) if you will have more than one of the same kind, for example "Ops team inbox".
  5. Tick the events it should get.
  6. Press Add channel. The channel appears in the channel list above the form.

Each kind has its own guide with the steps in the other service:

  • Email
  • Slack, Microsoft Teams, Discord and Telegram
  • PagerDuty
  • ntfy for free push to your phone
  • Webhooks and Zapier for your own systems
  • the HonkWatch app, which is turned on from the device itself, not from this form

Send a test

  1. On Alerts, find the channel in the list.
  2. Press Send test at the end of its row.
  3. Check that the message arrived. It is about a monitor called "Test monitor" and says it is a test alert from your alert settings.
  4. Look at Recently sent at the bottom of the page. The test shows as sent, or as failed with the reason.

A test goes only to the channel you pressed it on, whatever events are ticked. It sends a real message. You can send up to 10 test alerts an hour.

Sent means the other service accepted the message. It does not prove someone saw it, so check the inbox, channel or phone too.

Change or remove a channel

A channel cannot be edited once it is added. To change its address or its events, add a new channel with the right settings, send it a test, then press Remove on the old one.

Settings on each monitor

Some alert behaviour is set per monitor, under its settings when you add or edit it:

  • Repeat the down alert every (minutes, 0 = once). 0, the default, sends one down alert per outage. The shortest repeat is 5 minutes. Repeats stop when someone acknowledges the incident on the monitor's page.
  • Send a "back online" message when it recovers. On by default. If you turn it off, no channel gets a back up alert for that monitor, even with Back up ticked.
  • Alert when slower than (ms, optional). Empty means no slow alerts.
  • Warn before certificate expiry (days). 14 by default. Only website, keyword and SSL certificate monitors have it.
  • Down when this many locations agree and Each of them after this many failed checks in a row. These decide how sure we must be before a down alert goes out. See How checks work.

When alerts are not sent

  • During a maintenance window, new down, certificate and slow alerts and repeats are held back. If the monitor is still down when the window ends, the down alert goes out then. If an outage started before the window, its back up alert still goes out.
  • One outage sends one down alert, plus repeats if you set them. A monitor that keeps failing does not send a new alert on every check.
  • A paused monitor sends nothing.

A maintenance window with Tell people when it starts and ends ticked (it is by default) also sends a short notice when it starts and when it ends. The notice goes to your channels, but not to PagerDuty.

Limits and who can change alerts

  • Up to 50 alert channels per account. All channel kinds are on every plan.
  • Until you confirm your own email address (we send a link when you sign up), alerts can only go to that address. After you confirm it, you can add any channel.
  • Channels belong to the account, so everyone on your team shares them. Team members with the Viewer role can see them but cannot add, test or remove them. See Team members.

The box at the top of the Alerts page, Your alert setup, says how many channels will get outage alerts. If it says no channel is set to receive outage alerts, add one with Down ticked.

If alerts do not arrive

  1. Press Send test on the channel and check Recently sent. A failed line gives the reason.
  2. Check that the channel has the right event ticked. The Events column in the list shows them.
  3. Check the monitor's own settings above, such as the "back online" message.
  4. Follow the troubleshooting part of that channel's guide, or see I did not get an alert.
← Incidents Email alerts →

Still stuck? Email [email protected] and say which guide you were following.