mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Monitor Hierarchy to share setup. #3678
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#3678
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 @mcg1103 on GitHub (Oct 18, 2024).
📑 I have found these related issues/pull requests
I searched for "extend existing monitors" and "base monitor" but did not find any other feature requests.
🏷️ Feature Request Type
Maintenance
🔖 Feature description
Most of monitors on my system are the same except the URL and Friendly Name. I have been tweaking other setting to reduce false positives yet get notified of an outage as quick as possible. Would be cool to have a base monitor that you could change and the change would be applied to the other monitors that are based off that monitor.
✔️ Solution
Like the clone but the system maintains the connection between the two. Each field can either get a new value or get the value from the base monitor.
❓ Alternatives
No response
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Oct 20, 2024):
Sharing state as you are requesting is pretty error-prown and I don't think we should support this.
Something like the following seems much simpler in comparison (no tangling of monitors to some different system as suggested here).:
Duplicate of