monitor_heart Monitoring

Server alerts that reach your phone

Pipe alerts from Nagios, Monit, custom shell checks or your own services to a single mobile-friendly inbox. Push notifications when something breaks, forwarders to Discord and Slack.

Start free See pricing

error

The problem

Your monitoring stack (Nagios, Monit, scripts, Prometheus) is good at detecting problems but bad at notifying anyone. Emails go nowhere, internal Slack is muted by 9 PM, dedicated paging tools feel like overkill for three servers.

check_circle

How Alarum solves it

Send a curl POST to Alarum from any check that crosses a threshold. Alarum routes by level: critical hits push, warn lands in the inbox, info stays searchable. Forwarders mirror selected alerts to Discord or Slack.

Integrate in one line

A shell check that posts to Alarum when a threshold is crossed. Run it from cron, Monit, Nagios, or any orchestrator. Replace <YOUR_TOKEN> with an ingestion token from your project, then send.

#!/usr/bin/env bash
# check-disk.sh, alert when disk usage on / crosses 85%
USED=$(df / | awk 'NR==2 {gsub("%",""); print $5}')
if [ "$USED" -ge 85 ]; then
  curl -s -X POST https://alarum.me/h \
    -H "Authorization: Bearer <YOUR_TOKEN>" \
    -d "{
      \"level\": \"critical\",
      \"title\": \"Disk usage at ${USED}% on $(hostname)\",
      \"source\": \"$(hostname)\",
      \"tags\": [\"disk\", \"infra\"]
    }"
fi

Why teams pick Alarum for this

notifications_active

Push when it breaks

Critical alerts land on your phone via PWA push. Severities below "warn" stay in the inbox, no noise.

integration_instructions

Works with what you have

A single curl POST. Hookable from Nagios event handlers, Monit alerts, custom bash checks, Prometheus Alertmanager webhooks.

tag

Tag by host and service

tags=["host:db-01","service:postgres"] makes it trivial to filter which box or which service triggered the last alert.

nights_stay

Quiet hours, critical bypass

A disk-full at 3 AM still wakes you up. A "service restarted" at 3 AM stays silent.

forum

Forward to on-call channel

Pipe warn or critical to a Discord or Slack on-call room while the full noise stays in Alarum.

shield

Outbound only

Your servers push out. Nothing exposed to the public internet. Works behind NAT, behind a VPN, behind anything.

Why not just use X?

Datadog and PagerDuty are excellent at scale and priced for it. Alarum is the right fit when you already have a working monitoring layer that just needs a better notification destination: push to phone, mirror to chat, all in one place.

Related use cases

schedule

Cron job monitoring

Push notifications and a centralized timeline for every cron job. Get alerted the second a scheduled task fails, search past runs, forward failures to Discord or Slack.

Application error tracking

A no-friction error inbox. Pipe exceptions, 500s and background-job failures from any language to a single timeline. Sentry-lite for small teams.

Try it free, no card

Get started