Dynamically create multiple sub-Monitors based on `name`-parameters pushed to a primary PUSH monitor #1316

New issue

Open

opened 2026-02-28 02:17:09 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 02:17:09 -05:00

Owner

Originally created by @gautamsi on GitHub (Aug 5, 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

🔖 Feature description

Please add ability to auto-create monitors based on name parameter in PUSH url. Show the auto-created monitors as child of base monitor like hierarchy. It will also be helpful to add multiple parameters to push url which will auto-create unique monitors dynamically.

These monitors may also contribute to the final status of push monitor.

✔️ Solution

have several docker containers which have different name but similar kind of workload, say workers. These are dynamic numbers and I want to create ONE push monitor push different parameters to auto populate them in status page for monitoring. They may be cooldown period after which those orphaned monitors (not reporting in x hours/days) get auto cleaned.

I scale up and down those workers so it will be useful to have them show up in status page without manually pre-creating that many push urls.

❓ Alternatives

N/A

📝 Additional Context

No response

Originally created by @gautamsi on GitHub (Aug 5, 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 ### 🔖 Feature description Please add ability to auto-create monitors based on `name` parameter in PUSH url. Show the auto-created monitors as child of base monitor like hierarchy. It will also be helpful to add multiple parameters to push url which will auto-create unique monitors dynamically. These monitors may also contribute to the final status of push monitor. ### ✔️ Solution have several docker containers which have different name but similar kind of workload, say workers. These are dynamic numbers and I want to create ONE push monitor push different parameters to auto populate them in status page for monitoring. They may be cooldown period after which those orphaned monitors (not reporting in x hours/days) get auto cleaned. I scale up and down those workers so it will be useful to have them show up in status page without manually pre-creating that many push urls. ### ❓ Alternatives N/A ### 📝 Additional Context _No response_

deekerman added the

feature-request

A:monitor

A:api

type:enhance-existing

labels

2026-02-28 02:17:09 -05:00

deekerman commented

2026-02-28 02:17:14 -05:00

Author

Owner

@Lwtsde commented on GitHub (Jan 23, 2024):

Bump 2024!
I am receiving a JSON-Array with clients that I would love to automatically be monitors in a group!

@Lwtsde commented on GitHub (Jan 23, 2024): Bump 2024! I am receiving a JSON-Array with clients that I would love to automatically be monitors in a group!

deekerman commented

2026-02-28 02:17:14 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jan 23, 2024):

@Lwtsde
Please refrain from posting +1 / requests for updates things on issues, as this makes issue-management harder.
Issues are for discussing what needs to be done how by whom.
We use 👍🏻 on issues to prioritise work, as always: Pull Requests welcome.

Note that third party apis exist and that they might be better suited to your usecase. See https://uptime-kuma-api.readthedocs.io/en/latest/ for further details.
A first party api is coming, but this will take some time. See #3854 for further details.

@CommanderStorm commented on GitHub (Jan 23, 2024): @Lwtsde Please refrain from posting `+1` / requests for updates things on issues, as this makes issue-management harder. Issues are for discussing **what needs to be done how by whom**. [We use 👍🏻 on issues to prioritise work](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc), as always: [Pull Requests](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md) welcome. Note that third party apis exist and that they might be better suited to your usecase. See https://uptime-kuma-api.readthedocs.io/en/latest/ for further details. A first party api is coming, but this will take some time. See #3854 for further details.