You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
⚠️ Please verify that this feature request has NOT been suggested before.
I checked and didn't find similar feature request
🏷️ Feature Request Type
Other
🔖 Feature description
I have set up uptime kuma on the internal network as I have both internal and external servers to check. (More internal servers but over VPN)
I have a check to see if the current internet connection is up but in the case where this is down I do not want to check any dependent services as they are going to fail.
A more generic example if that I have 5 servers A B C D and E and if server A is down B C and D are also going to report as down even it just fixing Server A is going to resolve the issue with B C and D. So in this case I do not need to know about B C and D.
✔️ Solution
I think adding a dependency field on the monitor setup, so in may case above for B, C and D would have a dependency on Monitor A. Also a second field which will not set a timeout so that it can only check B, C and D if A has been checked within x amount of time.
❓ Alternatives
No response
📝 Additional Context
No response
The text was updated successfully, but these errors were encountered:
@gheydon
We are consolidating duplicate issues a bit to make issue management eazier.
I think, we should track this issue in #1089 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo)
=> I am going to close this as a duplicate
🏷️ Feature Request Type
Other
🔖 Feature description
I have set up uptime kuma on the internal network as I have both internal and external servers to check. (More internal servers but over VPN)
I have a check to see if the current internet connection is up but in the case where this is down I do not want to check any dependent services as they are going to fail.
A more generic example if that I have 5 servers A B C D and E and if server A is down B C and D are also going to report as down even it just fixing Server A is going to resolve the issue with B C and D. So in this case I do not need to know about B C and D.
✔️ Solution
I think adding a dependency field on the monitor setup, so in may case above for B, C and D would have a dependency on Monitor A. Also a second field which will not set a timeout so that it can only check B, C and D if A has been checked within x amount of time.
❓ Alternatives
No response
📝 Additional Context
No response
The text was updated successfully, but these errors were encountered: