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
Fallback notifications #923
Comments
I'd like to keep things as simple as possible and avoid a configuration UI where the user can say "deliver to channel A. If delivery fails, deliver to B." But perhaps we could have a fixed, predetermined fallback: when we detect a delivery failure, inform the account owner via email about it. We already do this for Signal notifications when Signal rejects our message due to rate-limiting on their end. We send a message to the account owner saying:
We could perhaps do something similar for other types of Signal failures, and for other channel types too. |
That makes sense.
For my use case, this would work, though having the ability to chose any notification method as the predetermined fallback seems like pure bonus cutomizability. |
@cuu508 These Signal rate-limits appear to be permanently imposed on new integrations (unchanged since at least Tuesday this week), is there any further insight into a solution beyond the blog post (which would seem to be outdated at this point)? |
@rebmcr since the blog post, I have not figured anything new on how to work around the Signal service's rate limits :-/ Can you please try the following:
And another thing to test:
When I view the Healthchecks account in the Signal app, I see it is marked as "Signal Connection". My guess is the being or not being a Signal Connection might influence the rate limiting logic. |
@rebmcr can you please share the phone number privately with me (send it to contact@healthchecks.io)? I'll poke around with sending Signal notifications to it (and you may get a test notification if it works out). |
Done! Thanks. |
I use Matrix and Email notifications for a few checks, although I realized I don't really need both at the same time. I only enabled Email since it is "more mature" than Matrix, in case something's off with my Matrix server.
The ideal solution would be to have a separate option for fallback notifications, which would be triggered/sent only if the primary notification method fails.
The text was updated successfully, but these errors were encountered: