[PR #1425] [MERGED] feat(docs): add ntfy-heartbeat-monitor to integrations page #1603

New issue

Closed

opened 2026-05-07 01:02:51 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-07 01:02:51 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/binwiederhier/ntfy/pull/1425
Author: @DerRockWolf
Created: 8/17/2025
Status: ✅ Merged
Merged: 8/17/2025
Merged by: @binwiederhier

Base: main ← Head: docs/integrations/heartbeat-monitor

📝 Commits (1)

9b97067 feat(docs): add ntfy-heartbeat-monitor to integrations page

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 docs/integrations.md (+1 -0)

📄 Description

I've written a small tool to implement heartbeat monitoring/alerting.
My main use-case is to be alerted if something in my alerting pipeline is broken.

It works by monitoring messages in a ntfy topic. If the last message is older than a given threshold, or if we can't retrieve the last message because the ntfy server is down/unavailable, a message is sent to a different ntfy topic (usually also on a different ntfy server).
If you have two or more "sites" you could monitor everything in a mesh like way 😄

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/binwiederhier/ntfy/pull/1425 **Author:** [@DerRockWolf](https://github.com/DerRockWolf) **Created:** 8/17/2025 **Status:** ✅ Merged **Merged:** 8/17/2025 **Merged by:** [@binwiederhier](https://github.com/binwiederhier) **Base:** `main` ← **Head:** `docs/integrations/heartbeat-monitor` --- ### 📝 Commits (1) - [`9b97067`](https://github.com/binwiederhier/ntfy/commit/9b97067b107400ff87706d7ac74c626503bde1df) feat(docs): add ntfy-heartbeat-monitor to integrations page ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/integrations.md` (+1 -0) </details> ### 📄 Description I've written a small tool to implement heartbeat monitoring/alerting. My main use-case is to be alerted if something in my alerting pipeline is broken. It works by monitoring messages in a ntfy topic. If the last message is older than a given threshold, or if we can't retrieve the last message because the ntfy server is down/unavailable, a message is sent to a different ntfy topic (usually also on a different ntfy server). If you have two or more "sites" you could monitor everything in a mesh like way :smile: --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>