Skip to content
StatusOwlDocs

Discord integration

Post rich embeds to any Discord channel via an incoming webhook.

Last updated May 9, 2026

The Discord integration uses an incoming webhook — no bot, no app installation. Each webhook posts to a single channel, so create one integration per channel you want to alert.

Creating the Discord webhook

  1. In Discord, open Server Settings → Integrations → Webhooks.
  2. Click New Webhook, name it (e.g. StatusOwl), and pick the target channel.
  3. Click Copy Webhook URL. It starts with https://discord.com/api/webhooks/.

Connecting it to StatusOwl

  1. Go to Integrations → Add Integration and choose Discord.
  2. Paste the webhook URL.
  3. Enter the channel name (display-only — used in the StatusOwl UI to identify the integration).
  4. Choose which events to subscribe to (see event coverage for what currently fires).
  5. Click Save, then Send Test to confirm delivery.

What currently sends to this integration

Per the integrations overview, Discord integrations receive:

  • Send Test events fired from the dashboard.
  • Watch Owl alert rules — when a host-metric rule routes to this integration, firing and resolving alerts post to the channel as color-coded embeds (red on fire, green on resolve).

Uptime-monitor state changes (down / recovery / maintenance) are configured on the integration but not yet dispatched. The flags are ready for the dispatch service when it ships.

Embed format

Live embeds for Watch Owl alerts include the rule name, host hostname, the metric and its current value, the threshold that tripped, and a timestamp. Color is severity-driven: red for fire, green for resolve.

Example, for a prod-db disk near full rule firing on prod-db-01.internal:

text
🔴 prod-db disk near full   (FIRED)
   Host:   prod-db-01.internal
   Metric: disk_percent = 94.2 (gt 90)
   Mount:  /var/lib/postgresql
   When:   2026-05-09 14:03 UTC

🟢 prod-db disk near full   (RESOLVED)
   Host:   prod-db-01.internal
   Metric: disk_percent = 76.1
   When:   2026-05-09 14:18 UTC

When uptime-monitor state-change dispatch ships, embed format for those events will be documented here.

See also