Parent/Child relation for good notification and good grafical uptime #1509

Closed
opened 2026-02-28 02:23:40 -05:00 by deekerman · 2 comments
Owner

Originally created by @mabed-fr on GitHub (Oct 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

UI Feature, Other

🔖 Feature description

My VPS is the child of the probe which pings google.fr because if I do not join google.fr it means that my internet access is down but not my VPS

✔️ Solution

add feature for have Parent/Child for good chart and alert

Alternatives

No response

📝 Additional Context

This feature allows not to calculate the uptime of my VPS while google.fr is DOWN

Originally created by @mabed-fr on GitHub (Oct 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 UI Feature, Other ### 🔖 Feature description My VPS is the child of the probe which pings google.fr because if I do not join google.fr it means that my internet access is down but not my VPS ### ✔️ Solution add feature for have Parent/Child for good chart and alert ### ❓ Alternatives _No response_ ### 📝 Additional Context This feature allows not to calculate the uptime of my VPS while google.fr is DOWN
deekerman 2026-02-28 02:23:40 -05:00
Author
Owner

@skaempfe commented on GitHub (Dec 30, 2022):

Like #1236 ?

@skaempfe commented on GitHub (Dec 30, 2022): Like #1236 ?
Author
Owner

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

@mabed-fr
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 and 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): @mabed-fr 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 and 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#1509
No description provided.