Steffen
My feedback
1 result found
-
68 votes
Hi all, there's now two options for that which are:
1. Through Zapier (we just added native Zapier integration): https://updown.uservoice.com/knowledgebase/articles/1911991 Using this you can connect pushover.net and receive alerts from updown.io. I'm keeping this suggestion "under review" to gather interest about a native integration with pushover.
2. Using a DigitalOcean function to catch the webhook and push it to pushover (contributed by Marc): https://github.com/MarcHagen/function-updownio-to-pushover
An error occurred while saving the comment An error occurred while saving the comment Steffen
commented
What would "{description}" contain and what other placeholders would there be? I have attached a screenshot of my current Updown.io -> Pipedream -> Pushover workflow such that you can see how I use it at the moment. Especially setting "priority" depending on whether something has gone down or come up seems useful.
(As a software developer I get your point that adding settings should be avoided when possible but IMHO not all settings are created equal. This would just be another option among the clearly labelled "Notifications" settings. It would not have any side-effects on other settings either. The Pushover API has been stable for years and the pricing is very attractive. All the workarounds using Pipedream/Zapier/DigitalOcean show that there is a real interest in getting Pushover working with updown.io.)
Steffen
supported this idea
·
An error occurred while saving the comment Steffen
commented
I wanted to completely switch to updown.io with our new server setup (we currently only use it as a limited secondary monitoring in addition to Pingdom). I especially like the IPv4 + IPv6 support that works out of the box without having to configure multiple checks per host.
But missing support for reliable push notifications is a deal-breaker for me: The dependence on Zapier for push notifications makes updown.io way more expensive than most of its competitors: 100 free Zapier "tasks" are more than enough in 99% of cases but we cannot risk missing notifications if shit really hits the fan. We'd therefore have to pay an additional $17 per month (Zapier's cheapest plan) just for Zapier to forward an HTTP request.
The alternative offered by updown.io don't work well for me: Slack is muted on my device in the after-work hours. Telegram is just shady and I'd have to somehow add an exception to allow a specific channel to disrupt my downtime (not sure if that's even possbile without allowing all channels to disrupt my downtime). I tried "Pushover notifications from e-mails" but unfortunately they are ugly walls of text.
Can you please reconsider adding native pushover support? It'd be easy to allow Pushover to disrupt downtime on my phone.
First of all, thank you for giving this some thought!
I think I would switch to any official implementation by updown.io in order to remove third-parties like Pipedream from the equation (even if that would mean loosing the "priority" feature). Realiability is paramount.
I'm not sure that turning Pushover into some kind of poweruser feature makes more sense than simply adding another notification option (or even 5 or 10 other). If configuration is more difficult it could lead to more support requests. And if it feels brittle/fragile that could make users nervous about getting their notifications, too. Another option would make the settings page longer but wouldn't necessarily make it more complex or overwhelming because it's just one list of service names that I can skim in seconds. (Maybe you could collapse individual notification sections unless they have been configured if you are concerned about UI real estate?)
Still, if you are more comfortable implementing this as some kind of "official webhook proxy" than that would be fine for me.