RMS Alerts and Notifications

What RMS alerts do

RMS alerts send notifications via email, SMS, or webhook when configured events occur on monitored devices. Trigger conditions include device going offline, device coming back online, reboot events, signal strength falling below a threshold, SIM switching, and configuration changes.

Alert trigger types

Trigger	Condition	Typical use
Device offline	Device stops reporting to RMS	Critical – device or link has failed
Device online	Device reconnects to RMS	Confirm recovery after outage
Device reboot	Device uptime resets	Detect unexpected restarts
Signal threshold	RSSI or RSRP falls below set value	Predict connectivity problems
SIM change	Device switches from SIM1 to SIM2 or vice versa	Track failover events on dual-SIM devices
Network operator change	Device registers to different network	Detect unexpected roaming
Firmware change	Device firmware version changes	Confirm OTA update completed

Alert delivery channels

Email – alert sent to one or more email addresses. Most common for non-critical monitoring.
SMS – SMS to a phone number via RMS SMS gateway. SMS credits are separate from device credits. Suitable for critical alerts requiring immediate attention.
Webhook – HTTP POST to a URL of your choice. Enables integration with Slack, Teams, PagerDuty, ticketing systems, or custom monitoring dashboards. The most flexible option for integration with existing NOC tooling.

Webhook integration

The webhook alert is particularly useful for organisations that already have a monitoring or alerting platform. When a trigger fires, RMS sends a JSON payload to the configured URL containing the device ID, event type, timestamp, and relevant metric values. This can be received by Slack incoming webhooks, PagerDuty event APIs, custom monitoring dashboards, or any HTTPS endpoint you control.