Configure status page to display based on tags #2233

New issue

Closed

opened 2026-02-28 02:47:26 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 02:47:26 -05:00

Owner

Originally created by @CommanderRedYT on GitHub (Jun 5, 2023).

⚠️ 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

You could add a way of saying that a certain status page will display all the monitors from a specific tag. Maybe even in a way that you can assign the tags for each group on the status page. Also, maybe a blacklist for tags would be a good idea, so you can just add a "no-display" tag to exclude it.

✔️ Solution

I for example would use that to automatically display status of services at home and on servers, and then split them via status groups for things like "Ping", "HTTP(S)", ....

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @CommanderRedYT on GitHub (Jun 5, 2023). ### ⚠️ 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 You could add a way of saying that a certain status page will display all the monitors from a specific tag. Maybe even in a way that you can assign the tags for each group on the status page. Also, maybe a blacklist for tags would be a good idea, so you can just add a "no-display" tag to exclude it. ### ✔️ Solution I for example would use that to automatically display status of services at home and on servers, and then split them via status groups for things like "Ping", "HTTP(S)", .... ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:47:26 -05:00

closed this issue
added the
feature-request

A:status-page
labels

deekerman commented

2026-02-28 02:47:32 -05:00

Author

Owner

@chakflying commented on GitHub (Jun 5, 2023):

Duplicate of #2810, #1609 and #965

@chakflying commented on GitHub (Jun 5, 2023): Duplicate of #2810, #1609 and #965

deekerman commented

2026-02-28 02:47:33 -05:00

Author

Owner

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

@CommanderRedYT Given that this is likely a duplicate: could you close this issue?
(only Louis and the you can do so. Duplicates just make things less manageable though)

@CommanderStorm commented on GitHub (Jun 6, 2023): @CommanderRedYT Given that this is likely a duplicate: could you close this issue? (only Louis and the you can do so. Duplicates just make things less manageable though)

deekerman commented

2026-02-28 02:47:33 -05:00

Author

Owner

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

Thanks ❤️

@CommanderStorm commented on GitHub (Jun 6, 2023): Thanks ❤️