ntfy
An open-source, self-hosted push notification service that sends notifications via simple HTTP PUT or POST requests. It is commonly used for system alerts and automated notifications.
Timeline (last 90 days)
L1 alert definition: risk of data loss, indicators of a security breach, outages of services with real external exposure, pushed via ntfy at high priority to wake the author, about five in total.
The author's monitoring stack is entirely self-hosted: Uptime Kuma for service availability, Netdata for system metrics, Scrutiny for disk SMART health, and ntfy for push, with no cloud dependency or SaaS fees.
ntfy is an open-source self-hosted push notification service that sends messages via HTTP PUT/POST and supports priority (min/low/default/high/urgent), tags, and click-through links.
The author implemented a circuit breaker with a single Postgres table, recording workflow_id, step_id, fail_count, last_fail, cleared_by, and cleared_at; two consecutive failures stop that step and send an ntfy alert, until it is reset after human confirmation. Since this mechanism was built, it has been triggered four times, catching issues such as rate limiting, malformed URLs, portal processing delays, and network timeouts.
All Facts (4)
L1 alert definition: risk of data loss, indicators of a security breach, outages of services with real external exposure, pushed via ntfy at high priority to wake the author, about five in total.
50%UnverifiedThe author's monitoring stack is entirely self-hosted: Uptime Kuma for service availability, Netdata for system metrics, Scrutiny for disk SMART health, and ntfy for push, with no cloud dependency or SaaS fees.
50%Unverifiedntfy is an open-source self-hosted push notification service that sends messages via HTTP PUT/POST and supports priority (min/low/default/high/urgent), tags, and click-through links.
50%UnverifiedThe author implemented a circuit breaker with a single Postgres table, recording workflow_id, step_id, fail_count, last_fail, cleared_by, and cleared_at; two consecutive failures stop that step and send an ntfy alert, until it is reset after human confirmation. Since this mechanism was built, it has been triggered four times, catching issues such as rate limiting, malformed URLs, portal processing delays, and network timeouts.
50%