Notification channels

A notification channel is where alerts are delivered. Until you add one, alerts are recorded but nobody hears about them.

Supported types#

Adding one#

1. Create the webhook in Slack or Discord and copy the URL.
2. In CloudPilot, add a channel, pick the type, and paste the URL.
3. Send a test so you know the path works before you need it.

That third step is the one people skip. A channel that was mistyped is indistinguishable from a quiet night.

Where the URL goes#

Webhook URLs are secrets — anyone holding one can post into your channel — so they are stored encrypted rather than in plain text. If the server is not configured with a key to encrypt them, CloudPilot refuses to save the channel rather than storing it unprotected.

Outbound requests are restricted#

CloudPilot validates webhook URLs before it will call them, and refuses ones that point at private or internal addresses. This stops the panel being used to reach things on your internal network that it should not be able to see.

If you are pointing a webhook at something on a private network, it will be refused. Give it a publicly reachable endpoint instead.

What gets sent#

• Uptime checks going down and recovering
• Resource alerts crossing their thresholds
• Servers going offline
• Certificates approaching expiry

Keeping alerts worth reading#

Route alerts to a channel people actually watch, and keep the volume low enough that a message there means something. A busy alerts channel is a channel nobody reads, which is the same as having no channel at all.