Grafana SMS & voice call notifications.

24/7 monitoring you can rely on.

Combine Grafana’s alerting engine with the reliability of the SMSEagle hardware gateway. Make sure you’re the first to know about a critical incident — even when the very network your monitoring stack depends on is the one that’s down.

Internet-independent alerting

Grafana detects the anomaly, but delivering that alert usually depends on your internet connection, an SMTP relay, or a cloud SMS provider. If any of these fail, the notification never arrives. SMSEagle sends alerts directly over the mobile network, so they get through even when your internet link is down.

Standalone hardware

Grafana and the systems it monitors often run on the same virtualized infrastructure – the same Docker host, the same VM cluster. If that platform goes down, your alerting can go down with it. SMSEagle is dedicated hardware with its own cellular connection. Your alerting gateway doesn’t share fate with the surrounding servers.

No cloud, full data control

SMSEagle runs on-premises. Alerts aren’t routed through a third-party cloud SMS provider — messages go straight from your own device over the cellular network to the mobile carrier, keeping alert data off external SaaS platforms.

How it works?

1 Event Trigger

A Grafana alert rule evaluates your metrics or logs and starts firing (e.g. min
(smseagle_modem_signal_strength) <30, or any Prometheus/Loki-based condition).

2 Communication

Grafana’s webhook contact point posts the alert notification to “smseagle-alert-webhook” — a small, open-source adapter running next to Grafana that translates it into an SMSEagle APIv2 request.

3 Alert

SMSEagle sends an SMS notification, or places a text-to-speech voice call, to the recipients defined for that alert.

Integrate in about 15 minutes

Grafana’s webhook contact point can’t talk to SMSEagle’s API directly — it needs a small translator in between. That translator, smseagle-alert-webhook, is a free, open-source, dependency-free adapter you deploy with a single docer compose up. Point a webhook contact point at it, and every alert rule you already have starts routing to SMS and voice calls — no changes to your rules required.

Monitoring is just the beginning.
Take full control of alerts and automation.

Per-alert channel & recipient routing

SMSEagle delivers Grafana alerts by SMS, voice call, WhatsApp or email from a single device, so urgent alerts reach people where they actually look.

Recipient and escalation groups

Not every alert should go to everyone, and a missed alert shouldn’t go nowhere. SMSEagle lets you define recipient groups, so each notification reaches the right team, and escalation groups make sure that if the first person doesn’t acknowledge, the alert moves on to the next responder.

Monitor Grafana itself

Who watches the watcher? If your Grafana server goes down, it can no longer send a single alert — and you might not find out until it’s too late. With SMSEagle’s built-in Network Monitoring, the gateway independently checks your Grafana server and sends an SMS or voice call the moment it stops responding.

Video tutorial: Grafana alerts via SMS & voice calls

Learn how to integrate Grafana with SMSEagle and deliver alerts through SMS messages and voice calls. This step-by-step tutorial covers API token configuration, webhook deployment, Grafana contact point setup, alert rule configuration, and live testing of both SMS and voice notifications.

1. SMSEagle configuration

Before you start: this is a self-hosted-only path. Grafana’s alerting engine must be able to reach the adapter, and the adapter must be able to reach your SMSEagle device on the LAN — so the clean fit is a self-hosted Grafana on the same network as the device. Grafana Cloud cannot reach a private LAN address; for that scenario, use SMSEagle’s Email-to-SMS poller instead.

Create a new user in SMSEagle (menu System > Users, user access level: “User”).
Create an API key for that user:
- go to Settings > Global settings > API and open the API v2 page
- click Create API key, fill in Key name and select the user created above as Owner
- Add access permissions in section Messages for: Send SMS
- Add access permissions in section Calls for: Make a ring call, Make a TTS Advanced call (for voice alerting)
- click Create key. The access token is shown only once, right after saving.

2. Deploy the adapter

git clone https://github.com/dmitrylambert/grafana-monitoring.git
cd grafana-monitoring/smseagle-alert-webhook
cp .env.example .env

Edit .env:

SMSEAGLE_API_URL — your device’s IP address or hostname
SMSEAGLE_ACCESS_TOKEN — the APIv2 token from step 1
SMSEAGLE_SMS_TO — default recipient number(s) (can be overridden per alert, see below)
keep SMSEAGLE_TEST_MODE=true until you’ve verified everything end to end

Build and start the container:

docker compose up -d --build
curl http://localhost:9099/healthz    # -> ok

Grafana configuration

3a. Grafana configuration — via the UI

Alerting → Contact points → Add contact point
- Name: SMSEagle
- Integration: Webhook
- URL: the adapter’s address as reachable from Grafana (e.g. http://host.docker.internal:9099/ if Grafana runs in Docker on the same host)
- HTTP Method: POST
- Click Test (with SMSEAGLE_TEST_MODE=true) to validate without sending a real SMS

Alerting → Notification policies — set SMSEagle as the default receiver, or add a matching route
On an alert rule, add label smseagle_channel: call for a voice call (omit it, or set sms, for a text), and optionally smseagle_to: +3712... to override recipients for that alert

3b. Grafana configuration — via provisioning files (recommended)

For a reproducible, GitOps-style setup, copy the example contactpoints.yaml, policies.yaml, and alert-rule.example.yaml files into your Grafana provisioning directory and restart Grafana. Edit the url: in contactpoints.yaml to your adapter’s address first.

Note: policies.yaml provisions the root notification policy — after this, all alerts route to SMSEagle by default, and the Notification Policies page becomes read-only in the UI. If you only want some alerts on SMSEagle, skip this file and add a route in the UI instead (see 3a).

Test it end to end

Keep SMSEAGLE_TEST_MODE=true while wiring things up: SMSEagle validates every request but doesn’t deliver it (a test send returns id: 0). Trigger a real alert rule and confirm delivery in docker compose logs -f, then flip the flag to false and rebuild for live delivery.

Good to know

Grafana sends a notification on both firing and resolved — tick “Disable resolved message” on the contact point if you only want the first one.
The SMS/call content is your alert’s message, summary, or description annotation, sent or read aloud verbatim, prefixed with PROBLEM. or RESOLVED. — no label dump, no firing counts, so what you type in the rule is exactly what’s delivered.

See also the detailed integration guide prepared by the Dmitry Lsmbert, available at: Github.

Explore SMSEagle Demo device

SMSEagle is a hardware & software solution that guarantees a swift delivery of your messages to designated recipients, whether it’s for notifications, alerts, or important updates.

After registering to a demo you get a remote access to our physical device NXS-9750.

14-days free trial
Access to over 20 functionalities

Integrations & Accessibility

Employee Communication

Customer Communication

Monitoring & Management

Security & Compliance

Developers

Support & Security

Evaluate

Learn