LibreNMS Push Notifications

Signalgrid is available as a native LibreNMS alert transport. You can connect LibreNMS directly to Signalgrid without installing a notification script or maintaining a custom webhook.

Once configured, LibreNMS can deliver network monitoring alerts, warning notifications, critical incidents, and recovery messages to your Signalgrid channel and registered iPhone or Android devices.

What You Need

• A current LibreNMS installation with the Signalgrid alert transport available
• A Signalgrid account
• Your Signalgrid Client Key
• Your Signalgrid Channel Token
• Outbound HTTPS access from the LibreNMS server to api.signalgrid.co

Create the LibreNMS Alert Transport

1. Sign in to the LibreNMS web interface
2. Open Alerts and select Alert Transports
3. Click Create alert transport
4. Enter a descriptive transport name, such as Signalgrid Production Alerts
5. Select Signalgrid as the transport type
6. Paste your Signalgrid Client Key
7. Paste your Signalgrid Channel token
8. Use LibreNMS's transport test to verify delivery, then save the transport

Required Fields

Connect the Transport to Alerting

Creating a transport makes Signalgrid available to LibreNMS, but the transport must also be used by your alerting configuration. Create or edit the relevant LibreNMS alert rule and operation, then select the Signalgrid transport as a notification target.

Your alert rule determines what LibreNMS monitors, while the operation controls when and where notifications are sent. This lets you use Signalgrid for device-down alerts, interface and port problems, sensor thresholds, service failures, network outages, and recovery notifications.

Severity Mapping

The native LibreNMS transport maps alert state and severity to the corresponding Signalgrid notification type automatically.

Notification Content

LibreNMS uses the alert title as the Signalgrid notification title and the rendered LibreNMS alert message as the notification body. You can customize that content with LibreNMS alert templates while keeping the native Signalgrid transport for delivery.

Test and Troubleshoot

• Send a test from the LibreNMS alert transport page and confirm that it appears in your Signalgrid channel
• If Signalgrid is not listed as a transport, update LibreNMS to a version that includes the native integration
• If authentication fails, verify the Client Key and make sure no spaces were added when copying it
• If the request succeeds but the alert goes to the wrong channel, verify that Channel contains the channel token rather than the channel name
• If no request is sent, confirm that the alert rule has an operation using the Signalgrid transport
• If delivery fails, verify that the LibreNMS server can reach https://api.signalgrid.co/v1/push over HTTPS