Where your alerts go

The channels

• Email Plain-text emails to any address. Your account email is the default.
• Slack A message in a Slack channel, through an incoming webhook.
• Discord A message in a Discord channel, through a channel webhook.
• Webhooks Signed JSON to your own HTTPS endpoint, for your own tools.

Email

Alerts arrive as plain-text emails from BBoxProbe. The subject is the alert; the text has the facts, what to do and a link to the monitor, and its last lines say why you get it and where to change that. Until you add a channel, every alert goes to your account email.

Website is down.
https://example.com/

Frankfurt and Virginia get 502 Bad Gateway.
Down since 10:32 UTC.

We'll email again when it's back.

Open the monitor: https://bboxprobe.com/monitors/ct3skrhd11sm

--
You get this because Website alerts go to your account email. Change it: https://bboxprobe.com/channels
BBoxProbe

To send alerts to another address, such as a team's shared inbox, add an Email channel with that address under Alert channels, then press Send a test on its card.

What every channel shares

• The same alerts. Outages, instability, a fast-burning error budget, slow answers and certificates close to expiry, each with a closing notice. How it works lists them.
• Per monitor, or all of them. A monitor can pick its channels. With none picked, its alerts go to every channel that's on, and with no channel on, to your account email.
• Retries, then email. A channel that fails an alert is tried again 1, 5 and 15 minutes later; after the last try, the alert goes to your account email, saying which channel couldn't take it.
• A test on demand. Send a test on a channel's card sends a test notice through it right away.
• A delivery log. The channels page lists the last 50 alerts and tests sent, with every channel's result: sent, failed or held.
• On or off. Turn a channel off to stop alerts going there without removing it.

Channels per plan

Every kind of channel is on every plan; your account email doesn't count as one.