Using healthchecks.io and ntfy.sh to wake you up if your services are down
fedilink
3

cross-posted from: https://discuss.ntfy.sh/post/3200

I use ntfy (on another instance) + healthchecks.io to wake me up at night when ntfy.sh is down (crazy inception, right?). It’s the “poor man’s PagerDuty” if you will. It works amazingly.

Here’s how I set it up:

  • I signed up healthchecks.io (free plan) and configured a project for “ntfy.sh” with a “ntfy” integration, i.e. publish to ntfy.example.com/<secret> with max priority
  • I have two different hosts execute small “integration ntfy.sh tests” and only ping healthchecks.io if they succeed. If they don’t healthchecks.io will publish to ntfy.example.com/<secret>
  • In the ntfy Android app, I subscribe to ntfy.example.com/<secret>, enable “Keep alerting on highest priority”, and make it override DND (do not disturb) for this topic.

Now when ntfy.sh goes down, the integration tests in the cronjobs will fail, and so healthchecks.io will not be pinged, which will trigger it to publish to ntfy.example.com/<secret> and let my phone consistently ring until I acknowledge it.

(Disclamer: I am the maintainer of ntfy. Hope posting this is fine. Happy to answer questions; I also have a brand new ntfy community, feel free to join)

@cyps@lemmy.world
link
fedilink
English
11Y

I just have to say, I really love ntfy.

Years ago I used an app called simplepush, even bought the premium key. Installed it half a year ago and now they’ve changed to a yearly subscription. Fair enough. So I thought about throwing something together in python just to replicate the functionality just for my personal use… but luckily I searched and found ntfy first.

Really appreciate the work.

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 279 users / day
  • 589 users / week
  • 1.34K users / month
  • 4.55K users / 6 months
  • 1 subscriber
  • 3.5K Posts
  • 70K Comments
  • Modlog