Dependent entities #1582

Closed
opened 2026-02-28 02:26:14 -05:00 by deekerman · 2 comments
Owner

Originally created by @derekoharrow on GitHub (Nov 24, 2022).

⚠️ 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

In some situations, you may have a service that is dependent upon another service being available.

For example, you may wish to do an HTTP GET on a URL to check if a website is up. But that HTTP GET request may be dependent on your DNS server working.

So, you may have multiple related monitors - one for DNS and one for HTTP in this example.

It would be great to be able to list/tag the monitors that a monitor is dependent on. In this case, the HTTP monitor is dependent upon the DNS monitor.

There is no point checking the HTTP monitor if the DNS monitor is down, and the HTTP monitor state can be assumed as down if the dependent DNS service is down too (optional).

✔️ Solution

Add a multi-select to each Monitor that allows you to select which other monitors it is dependent upon.

If any of those dependent monitors are down, then there is no point monitoring the parent monitor and it's state can be assumed as down.

Alternatives

No response

📝 Additional Context

No response

Originally created by @derekoharrow on GitHub (Nov 24, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description In some situations, you may have a service that is dependent upon another service being available. For example, you may wish to do an HTTP GET on a URL to check if a website is up. But that HTTP GET request may be dependent on your DNS server working. So, you may have multiple related monitors - one for DNS and one for HTTP in this example. It would be great to be able to list/tag the monitors that a monitor is dependent on. In this case, the HTTP monitor is dependent upon the DNS monitor. There is no point checking the HTTP monitor if the DNS monitor is down, and the HTTP monitor state can be assumed as down if the dependent DNS service is down too (optional). ### ✔️ Solution Add a multi-select to each Monitor that allows you to select which other monitors it is dependent upon. If any of those dependent monitors are down, then there is no point monitoring the parent monitor and it's state can be assumed as down. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_
deekerman 2026-02-28 02:26:14 -05:00
Author
Owner

@mabed-fr commented on GitHub (Dec 7, 2022):

Like https://github.com/louislam/uptime-kuma/issues/2261 ?

@mabed-fr commented on GitHub (Dec 7, 2022): Like https://github.com/louislam/uptime-kuma/issues/2261 ?
Author
Owner

@CommanderStorm commented on GitHub (Dec 1, 2023):

@derekoharrow
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in https://github.com/louislam/uptime-kuma/issues/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

@CommanderStorm commented on GitHub (Dec 1, 2023): @derekoharrow We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in https://github.com/louislam/uptime-kuma/issues/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
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#1582
No description provided.