Notification channels and rules
1. Set up e-mail sending (for e-mail channels)
Section titled “1. Set up e-mail sending (for e-mail channels)”-
Admin › Notifications › E-mail providers › New provider
SMTP or Amazon SES, with the Send from address. One provider is the default.
2. Add a channel
Section titled “2. Add a channel”-
Channels tab › New channel, then pick the Type
-
Fill in what that type needs
-
Email - recipients, one per line; optionally a provider other than the default.
-
Slack / Teams - the incoming webhook URL.
-
Telegram - the bot token from BotFather and the chat id or @channel.
-
Webhook - an https URL; requests carry a signed
bmp.event/v1envelope. -
Heartbeat - a Healthchecks.io or Uptime Kuma push URL and the minutes between pings.
-
-
Save, then click Send test
A real message goes out and the result shows at once. A tested channel ticks off the first-run checklist.
3. Add a rule
Section titled “3. Add a rule”-
Rules tab › New rule
-
Choose the Events and the Lowest severity
For backup failures, Failures in a row before it alerts avoids noise from a single blip; 1 alerts at once.
-
Choose Send to - one or more channels
-
Optionally narrow it
By Environments, Server tags, Plans or Servers. Empty means everything in scope.
-
Optionally set Quiet hours
Non-critical messages are held back during those hours, in the zone you pick. Critical ones always go out.
The heartbeat
Section titled “The heartbeat”A Heartbeat channel pings an outside monitor every few minutes only while the platform is healthy. If the pings stop, that monitor alerts you - the one way to hear that the platform itself is down. Set the monitor’s period to match, with some grace.