[Moved to Roadmap] Add ntfy.sh and shoutrrr Alert services

Feature Requests
,
1

Shoutrrr and ntfy.sh would be welcome additions to the list of alert services. They are free to use and ntfy would allow for push notifications. I’m currently using shoutrrr in ddns-updater to push alerts to ntfy.shand it would be great to use for system alerts.

1 Like
2

You can use the Slack option and paste the https://ntfy.sh/topic URL in the “Webhook URL” field. Notifications will show up as {"text": "TrueNAS @ truenas \n \nThis is a test alert\n\n"}. A bit ugly but works.

3

Thanks for that. Your right. A little messy but it works

4

But I also think it’ll be nice if we can support ntfy (and possibly other services that use webhook and expect plaintext instead of {"text": "..."}). (upvoted)

5

Better yet, try using this as your Slack webhook URL: https://ntfy.sh/topic?tpl=yes&t={{.text}}&md=yes.
See all things you can do with query parameters here: Sending messages - ntfy

3 Likes
6

Howdy…did you have to install Watchtower to use shoutrrr notifications with ddns-updater? I’d like to setup email alerts when my public IP changes.

7

For those with ntfy coming back here, I made one change which makes a big difference in formatting.

https://ntfy.sh/topic?tpl=yes&m={{.text}}&md=yes

...t={{.text}}... puts the alert alert into the title of the ntfy alert, whereas ...m={{.text}}... puts the alert text into the message body.

Thanks for figuring it out originally though, @helium !

1 Like
8

Adding on to this, this abomination:
https://ntfy.sh/topic?tpl=1&md=1&m=%7B%7B%24p%20%3A%3D%20splitn%20%22%5Cn%5Cn%22%202%20.text%7D%7D%7B%7B%24p._1%20%7C%20trim%7D%7D

…looks sus but decoded its just this:
{{ $p := splitn “\n\n” 2 .text }}{{ $p._1 | trim }}

which basically trims the ugly TrueNAS @ truenas and leaves just the info-message itself.

I also tried via smtp → mailrise → ntfy but it doesnt really have any advantages (i.e. no alert level in subject, the slack-method is also one hop less.

1 Like
9

Update: Moved to Roadmap for Assessment

Great news! This feature request has been transferred to our internal roadmap for detailed scoping and assessment.

What this means:

  • Our product and technical documentation team will now evaluate technical feasibility, resource requirements
  • This request is now closed for voting, and your votes have been released back to use on other requests
  • Please note that transfer to the roadmap doesn’t guarantee implementation - some features may not proceed based on our assessment findings, however we will update this thread once a decision has been made.

Thank you to everyone who voted and contributed to the discussion. Your input has been invaluable in helping us understand the community’s needs and use cases for this feature.

2 Likes