mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Dependent entities #1582
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#1582
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @derekoharrow on GitHub (Nov 24, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ 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
@mabed-fr commented on GitHub (Dec 7, 2022):
Like https://github.com/louislam/uptime-kuma/issues/2261 ?
@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
DOWNandUP#3112DOWNandUP#3115