Beszel

Beszel notifies through Shoutrrr URLs. Its generic webhook sends only a title and a message, with no status field and no alert id. The Beszel preset reads everything it needs from the title: whether the alert fires or recovers, which system it is about, and which earlier alert a recovery closes. Checked against the alert texts of Beszel 0.21.

1. Create the alert source in UptimeifyCopy Anchor Link

Go to Incident Management → Alert Sources → New, pick the Beszel preset, name it, and create it. The success screen shows a ready-made notification URL for Beszel:

generic://<your-domain>/api/im/ingest/<token>?template=json

It is shown once and never displayed again in cleartext. If you lose it, rotate the token from the source's Settings tab and build the URL again from the new ingest URL: replace https:// with generic:// and append ?template=json.

template=json is required. Without it Beszel sends plain text instead of { "title", "message" }, and the preset has nothing to read.

2. Add the URL in BeszelCopy Anchor Link

1. In Beszel, open Settings → Notifications.
2. Under Webhook / Push notifications, add the URL from step 1 and save. Test URL sends a test notification. It arrives as an open alert titled Test Alert; resolve it by hand.
3. In the systems table, open the bell icon of each system and enable the alerts you want (status, CPU, memory, disk, and so on).

Beszel sends one notification when an alert fires and one when it recovers. Both reach the same Uptimeify alert, so the recovery resolves it.

Supported alert typesCopy Anchor Link

Beszel sends no recovery for SMART and ZFS. Those alerts stay open until you resolve them in Uptimeify. Several unhealthy containers on one system share one alert, because Beszel's recovery also covers the whole system.

Default field mappingCopy Anchor Link

Severity mapCopy Anchor Link

Sample payloadCopy Anchor Link

{
  "title": "backend1 CPU above threshold",
  "message": "CPU averaged 91.20% for the previous 10 minutes.\n\nhttps://beszel.example.com/system/x8k2m4p9q1w7e3r"
}

You can send this exact payload against your source's mapping from the Payload Mapping tab in the dashboard to verify the setup before enabling alerts in Beszel.

Beszel by email insteadCopy Anchor Link

If Beszel can only reach you by email (SMTP under Settings → Notifications), use an Email source instead. Beszel's email subject is the same title, and the body is the message followed by the link. Set these emailSelectors through the Alert Sources API to get the same behavior as the webhook preset:

{
  "emailSelectors": {
    "title": "subject",
    "severity": "subject =~ /^SMART (failure) on / || subject =~ /^Storage pool (FAULTED|OFFLINE|UNAVAIL|REMOVED|SUSPENDED) on / || subject =~ /^Connection to .+ is (down)\\b/ || subject =~ /^(Failed) services on / || subject =~ /^Storage pool (DEGRADED) on / || subject =~ /^SMART (warning) on /",
    "status": "subject =~ / (battery (?:above|below)) threshold/ || subject =~ / (above|below) threshold/ || subject =~ /^Connection to .+ is (down|up)\\b/ || subject =~ /^Network monitor (loss|recovered) on / || subject =~ /^Services (recovered) on / || subject =~ /containers are (healthy)\\b/",
    "host": "subject =~ /^(.+?) (?:\\d+m load|\\S+) (?:above|below) threshold/ || subject =~ /^Connection to (.+) is (?:down|up)\\b/ || subject =~ /^Network monitor (?:loss|recovered) on (.+?): / || subject =~ /^(?:Failed services|Services recovered) on (.+) \\S+$/ || subject =~ /^(?:Unhealthy container \\S+|\\d+ unhealthy containers) on (.+) \\S+$/ || subject =~ /^(.+) containers are healthy\\b/ || subject =~ /^SMART \\S+ on (.+?): / || subject =~ /^Storage pool \\S+ on (.+?): /",
    "dedupKey": "subject =~ /^(.+) (?:above|below) threshold/ || subject =~ /^(Connection to .+) is (?:down|up)\\b/ || subject =~ /^Network monitor (?:loss|recovered) (on .+)$/ || subject =~ /^(?:Failed services|Services recovered) (on .+) \\S+$/ || subject =~ /^(?:Unhealthy container \\S+|\\d+ unhealthy containers) on (.+) \\S+$/ || subject =~ /^(.+) containers are healthy\\b/ || subject =~ /^(SMART \\S+ on .+?) \\S+$/ || subject =~ /^(Storage pool .+)$/",
    "severityMap": { "failure": "sev1", "FAULTED": "sev1", "OFFLINE": "sev1", "UNAVAIL": "sev1", "REMOVED": "sev1", "SUSPENDED": "sev1", "down": "sev2", "Failed": "sev2", "DEGRADED": "sev2", "warning": "sev3" },
    "resolveValues": ["below", "battery above", "up", "recovered", "healthy"],
    "custom": { "details": "body =~ /^(.*?)\\s*https?:\\/\\/\\S+\\s*$/s || body" }
  }
}

The webhook preset is the better choice where it works: it also stores the Beszel link as the incident's link.