NTFY Transport

Feature Requests
1

Hi,

Is there anyone who wrote a transport for the NTFY product in Librenms transport?

Or is there anyone who integrates with the NTFY product?

Best Regards

1 Like
2

You could use the default API Transport for NTFY. This is our config:

API Method: POST
API URL: https://ntfy.sh/your-topic-here
Options:
headers: Content-Type: text/plain
body: {{ $title }} {{ $msg }}
Auth Username:
Auth Password:

1 Like
3

I am self hosted. I had to enable SMTP on my NTFY server for some other devices. I just send email to the NTFY server from LibreNMS. It works OK.

4

I’ve been using API transport for ntfy, but there’s a case where a dedicated transport might be useful.

If you set Priority=urgent for a down event ntfy can trigger a persistent alert in the app that alarms continuously until acknowledged. I can manually set this in the API transport headers, but it means that recovery alerts are also tagged as urgent when I’d rather that they weren’t (when asleep, I want to be woken by a system down event, but not by a recovery event).

From the ntfy docs:

Priority ID Name Description
Max priority 5 max/urgent Really long vibration bursts, default notification sound with a pop-over notification.
High priority 4 high Long vibration burst, default notification sound with a pop-over notification.
Default priority 3 default Short default vibration and sound. Default notification behavior.
Low priority 2 low No vibration or sound. Notification will not visibly show up until notification drawer is pulled down.
Min priority 1 min No vibration or sound. The notification will be under the fold in Other notifications.

If anyone has a workaround for setting ntfy status to correspond roughly with LibreNMS severity, I’d be grateful.