mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
composed checks #566
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#566
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 @rubvaz on GitHub (Nov 16, 2021).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
Other
🔖 Feature description
Some applications may need a composed check to have correct a proper operation
✔️ Solution
In my case we need that more than one check to have an application working, so if one of the checks is down all the composed check should be done.
❓ Alternatives
No response
📝 Additional Context
No response
@deefdragon commented on GitHub (Nov 17, 2021):
Are you referring to only marking something as up/down based on the combination of the statuses of a group of monitors? Or are you describing having a monitor know that it relies on another monitor, and if that monitor is down, automatically going down?
Regardless, going to reference #468 (216 specifically) as I think this is a duplicate, but if you have more details/believe its not a duplicate, feel free to expand on the problem.
@chakflying commented on GitHub (Dec 6, 2023):
Closing as we now have support for group monitors (#2693). Specific issues with group monitors should be tracked elsewhere.