Notification Channels

Notification channels define where alerts are delivered when an incident or performance issue occurs.

What Are Notification Channels?

Notification channels are destinations where alert notifications are sent. You can configure multiple channels and reuse them across different alert rules.

At least one notification channel must be created before alerts can be enabled.

Available Notification Channels

  • Email
  • Slack
  • Microsoft Teams
  • Discord
  • Webhook

Creating a Notification Channel

  1. From the left sidebar, navigate to Alerts.
  2. Open the Notification Channels tab.
  3. Click + Add Channel.
  4. Enter a name to identify the channel.
  5. Select the notification type.
  6. Fill in the required configuration fields.
  7. Click Save Channel.

Email Notifications

Enter the email address where you want to receive alerts.

Note: Email notifications are only supported for downtime-type alerts.

Microsoft Teams Notifications

Microsoft Teams notifications are delivered using an incoming webhook URL.

  1. Open Microsoft Teams and select the desired team and channel.
  2. Click the channel menu and choose Connectors or Workflows.
  3. Create an Incoming Webhook.
  4. Copy the generated webhook URL.
  5. Paste the URL into the Teams webhook field.

Slack Notifications

Slack notifications are sent via incoming webhooks.

  1. Go to your Slack workspace.
  2. Create or select the channel you want to receive alerts in.
  3. From Slack settings, add an Incoming Webhook.
  4. Authorize the app and select the channel.
  5. Copy the webhook URL and paste it into the Slack webhook field.

Discord Notifications

Discord notifications use channel webhooks.

  1. Create or open a Discord server.
  2. Select the channel where you want alerts.
  3. Open Server Settings → Integrations → Webhooks.
  4. Create a new webhook for the channel.
  5. Copy the webhook URL and paste it into the Discord webhook field.

Webhook Notifications

Webhook notifications send alert events to a custom HTTP endpoint of your choice. This allows you to integrate alerts with internal systems, automation tools, or third-party services.

Enter the URL where you want to receive alert events. Your endpoint must accept HTTP POST requests with a JSON payload.

Webhook Payload Structure

{
  "event": "alert_triggered",
  "alert_type": "downtime | latency",
  "summary": "Short alert title",
  "details": "Detailed alert description",
  "current_value": "Measured value at the time of alert",
  "timestamp": "2025-01-01T12:00:00Z"
}

The payload fields are defined as follows:

  • event — The event type. Currently always alert_triggered.
  • alert_type — The type of alert that was triggered (downtime or latency).
  • summary — A short, human-readable alert title.
  • details — Detailed context about the alert, including the affected website, monitor, or service.
  • current_value — The value that caused the alert to trigger (for example, response time in milliseconds).
  • timestamp — ISO 8601 timestamp indicating when the alert was triggered.

Your webhook endpoint should respond with a 2xx status code to acknowledge receipt of the alert. Non-success responses may result in retries.

Testing & Managing Channels

After saving a channel, you can manage it from the actions menu.

  • Send a test notification
  • Edit channel configuration
  • Delete the channel

Using Channels in Alerts

Once a notification channel is configured, it can be selected when creating or editing alert rules.

Multiple alert rules can share the same notification channel.