Notification channels (email, Discord, and webhook)

Summary#

CloudStats can notify you through email, a Discord incoming webhook, a generic HTTPS webhook, or any combination of those. A metric or availability alert rule can use several channels, one channel, or no channels. If a rule has no channels, CloudStats can still evaluate the rule, but it does not send notifications.

Prerequisites#

• A CloudStats account
• An email address you control, a Discord incoming webhook HTTPS URL, and/or a publicly reachable HTTPS URL that can receive JSON POST requests
• At least one metric alert rule or server availability alert if you want alert delivery (you can also send a test from a channel)

Set up a channel#

In the CloudStats app, create a notification channel and choose one type:

Email#

Enter one destination email address for that channel. CloudStats sends alert mail to that address. One email channel holds one address.

Email subjects:

• Firing metric alert: [CloudStats] <severity>: <alert name> on <server>
• Resolved metric alert: [CloudStats] Resolved: <alert name> on <server>
• Server down: [CloudStats] Server down: <server>
• Server recovered: [CloudStats] Server recovered: <server>
• Test: [CloudStats] Test notification

The message body includes the server, alert name, severity, state, and, for metric alerts, the metric, value, and threshold. It also includes a link to https://app.cloudstats.me. CloudStats emails do not include passwords or credentials.

Discord#

Use a Discord incoming webhook HTTPS URL. CloudStats posts an embed that includes the alert name, server, severity, metric, value, and threshold (and a fired-at time except on a test). Use HTTPS only.

Webhook#

Use a publicly reachable HTTPS URL. CloudStats sends a JSON POST body. Use HTTPS only.

The event field is one of:

• alert.firing
• alert.resolved
• server.down
• server.up
• notification.test

The JSON object includes these fields:

• event
• event_id
• organization with id
• server with id, hostname, and name
• alert with name
• state
• metric
• value
• threshold
• severity
• timestamp (UTC, RFC 3339)

Example shape for a firing metric alert:

{
  "event": "alert.firing",
  "event_id": "...",
  "organization": {"id": "..."},
  "server": {"id": "...", "hostname": "...", "name": "..."},
  "alert": {"name": "..."},
  "state": "FIRING",
  "metric": "cpu.utilization.percent",
  "value": 91.5,
  "threshold": 90,
  "severity": "critical",
  "timestamp": "2026-08-22T18:00:00Z"
}

CloudStats delivers webhooks only to public addresses. URLs that point to private, loopback, or instance-metadata addresses are not delivered.

Attach channels to a rule#

When you create or edit an alert rule, you can attach none, one, or several channels. Channels are optional. An empty channel list means the rule will not send notifications.

Slack and Telegram are not available as CloudStats notification channel types.

Send a test#

The CloudStats app can send a test notification on a channel. A completed test means CloudStats attempted the delivery. It does not guarantee that your email inbox, Discord server, or webhook receiver has already shown the message.

If the test reports that the dispatcher did not complete the test in time, try again later. See Troubleshoot alert and notification delivery.

Expected behavior#

• Email, Discord, and webhook are the supported customer channel types.
• A rule may notify some or all of those types, or none.
• Firing and resolved metric alerts, server-down and server-recovered notices, and tests each produce the matching event name above.
• While an alert stays in the same firing or server-down state, CloudStats does not keep sending the same notice. See Create and manage metric alert rules and Server availability alerts.

Troubleshooting and limitations#

• Use HTTPS URLs for Discord and webhook channels.
• A successful test is not a promise that a downstream inbox has received the message. Check spam folders for email, and confirm the Discord or webhook URL is current and publicly reachable.
• Do not send CloudStats your Discord webhook URL or mailbox credentials in a support ticket unless a human already asked for a specific safe detail. Prefer redacting secrets.
• If a rule has no channels, missing mail or chat messages are expected.

Related articles#

• Create and manage metric alert rules
• Server availability alerts
• Troubleshoot alert and notification delivery