Monitor Hierarchy to share setup. #3678

Closed
opened 2026-02-28 03:37:32 -05:00 by deekerman · 1 comment
Owner

Originally created by @mcg1103 on GitHub (Oct 18, 2024).

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

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_
deekerman 2026-02-28 03:37:32 -05:00
Author
Owner

@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

@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).: - #1323 - #455 Duplicate of - #937
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#3678
No description provided.