-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to setup a second notification channel to be used only when the first is down ? #4686
Comments
How do you determine that ntfy is down? |
if the notification from uptime kuma doesn't go through ntfy i think it reply with an error code like 404 or similar , so in this way uptime kuma can select the second notification method |
I don't quite get what you want to convey here. |
i'll try to explain: as much as i can , i self host everything but i need to have a least external way to get notification if something very bad happend , that's why i ask for a failover on notification |
i want to add that if my notification system is down doesn't mean that everything is on fire...maybe just this docker container is exited and other system are in good shape...that's why we have two system for both critical services we host ; if one goes down no problem to hurry to solve....even in weekend but i cannot have 2 system for hosting 2 ntfy because ip address change and i have no failover system on uptime kuma |
Then why don't you route the alerts that the chat system (or whatever critical piece of infra) is down via all notification channels (including said group)? |
What do you mean by this part. You likely have some sort of reverse proxy in front of said contaiers => why not handle this redundancy in traefik/nginx? |
do you mean to setup a default notification channel to external pushover system instead of ntfy? |
Because in that case i should install another instance of ntfy container on another host that must have another ip + add traefik/nginx on a third host and setup al the stuff...i think is complicated and i don't have a third host |
If your self-hosted chat system fails, then yes: |
my infra is very critical since all services are provided from the main HQ. |
Sorry, but I think solving your need via the existing tools is sufficient to solve your usecase. Just add a monitor to monitor your notification provider which notifies via an external provider?1 This Feature request is closely related to #1315 I think that failovers and business continuity should be handled by the notification provider. Footnotes |
I have the same setup. Kuma with ntfy. You can go on and on like this. "Who watches the watchmen?" 🥸 |
🛡️ Security Policy
📝 Describe your problem
Hi , i have installed uptime kuma and setup ntfy notification
ntfy is self hosted in our datacenter , how can i setup for example pushover or another external notification service to be used only if ntfy for some reason is down?
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.11
💻 Operating System and Arch
docker
🌐 Browser
chrome - firefox
🖥️ Deployment Environment
docker
The text was updated successfully, but these errors were encountered: