-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Enhancement: Thresholds #49
Comments
We’ve got this covered already in #21 Retries: for instance 3 retries in xx seconds before a service is being marked as down |
Thanks for pointing out. Hadn't seen that when looking if it was already mentioned. |
I get what you mean! Makes sense. Cheers! |
Agree with this, I actually added version number in the frontend which mentioned in #21, but it is hard to mark as resolved. |
@louislam |
I just discovered that github provides checkbox syntax. Maybe you can prepend a checkbox for each request, so that I can mark as resolved. |
@louislam done! |
Implemented in 1.0.7 |
Thanks for this project!
Its lean and seems to work so far!
What I'd really love to see extended is the notification functionality.
Wouldn't it be nice to have a threshold, for example for Pings, before an Alarm triggers?
my Internet pretty much disconnects every 8-48 hours once for 1-2 minutes.
Would be cool to tell Uptime Kuma to only send a notification if minimum X failed attempts happened.
Thanks for considering!
The text was updated successfully, but these errors were encountered: