Create dashboard with all monitors with specific tag #1146

Closed
opened 2026-02-28 02:11:30 -05:00 by deekerman · 5 comments
Owner

Originally created by @acdoussan on GitHub (Jun 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

I'd like to be able to create a dashboard based off of a tag, or some set of tags, and have the dashboard automatically include all monitors with that tag. If a new monitor is created with a tag, that monitor should automatically be included in the dashboard.

✔️ Solution

Maybe a toggle on the UI that lets you switch between choosing monitors or tags? Or, allow the user to choose either tags for a group, or select individual monitors.

Alternatives

No response

📝 Additional Context

No response

Originally created by @acdoussan on GitHub (Jun 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 I'd like to be able to create a dashboard based off of a tag, or some set of tags, and have the dashboard automatically include all monitors with that tag. If a new monitor is created with a tag, that monitor should automatically be included in the dashboard. ### ✔️ Solution Maybe a toggle on the UI that lets you switch between choosing monitors or tags? Or, allow the user to choose either tags for a group, or select individual monitors. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_
deekerman 2026-02-28 02:11:30 -05:00
Author
Owner

@QuentinDEME97 commented on GitHub (Jan 20, 2023):

+1 for this.

Would be also nice to sort or group by monitors by label.

@QuentinDEME97 commented on GitHub (Jan 20, 2023): +1 for this. Would be also nice to `sort` or `group by` monitors by label.
Author
Owner

@CommanderStorm commented on GitHub (May 19, 2023):

@QuentinDEME97 @mutasim please show your support by adding tumb-ups to the issue and not commenting +1 or similar, as this makes issue management way harder.

I will be a bit harsh: This is the GitHub version of grafittis

@CommanderStorm commented on GitHub (May 19, 2023): @QuentinDEME97 @mutasim please show your support by adding tumb-ups to the issue and not commenting `+1` or similar, as this makes issue management way harder. I will be a bit harsh: This is the GitHub version of grafittis
Author
Owner

@CommanderStorm commented on GitHub (Jun 11, 2023):

@acdoussan a very similar feature has been implemented+merged.
Any version after 1.22.0-beta.0 supports this.
image
image

Could you close this Issue, if this has been resolved?

@CommanderStorm commented on GitHub (Jun 11, 2023): @acdoussan a very similar feature has been implemented+merged. Any version after [`1.22.0-beta.0`](https://github.com/louislam/uptime-kuma/releases/tag/1.22.0-beta.0) supports this. ![image](https://github.com/louislam/uptime-kuma/assets/26258709/2b8673a3-214f-449f-a7fd-675c6dacc8db) ![image](https://github.com/louislam/uptime-kuma/assets/26258709/2a188e08-0774-402e-92e7-c18da04c0026) Could you close this Issue, if this has been resolved?
Author
Owner

@CommanderStorm commented on GitHub (Jun 11, 2023):

If not, is this a duplicate of https://github.com/louislam/uptime-kuma/issues/651?

@CommanderStorm commented on GitHub (Jun 11, 2023): If not, is this a duplicate of https://github.com/louislam/uptime-kuma/issues/651?
Author
Owner

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

@acdoussan
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #651 as there is no functional difference
⇒ I am going to close this as a duplicate.

@CommanderStorm commented on GitHub (Dec 5, 2023): @acdoussan We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in #651 as there is no functional difference ⇒ 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#1146
No description provided.