Self-Hosted ntfy Removed an External Delivery Dependency
The alert sink originally targeted a public ntfy service, which made production notification depend on infrastructure outside the hserver control boundary.
The alert sink originally targeted a public ntfy service, which made production notification depend on infrastructure outside the hserver control boundary.
Moving alert delivery to authenticated self-hosted ntfy introduced a publisher token that the alert-sink needs at runtime.
Delivery counters only change when an alert is sent, so a quiet system could leave a dead notification service unnoticed for hours.
An alert can fire correctly and still never reach the operator if Alertmanager or the external delivery path fails.