Public / Anonymized status page

[DennisGaida]

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

With public-facing uptime-kuma instances, you get to see the friendly names of the monitors on a status page. This could have security / privacy implications if you e.g. had monitors for secret-foo-server.domain.local and secret-bar-server that nobody should know about.

✔️ Solution

Two things would be beautiful:

1. Create a status page that contains no monitors, but in the backend still uses monitors to output "All Systems Operational". It would pretty much just mean an option on the settings page to hide all monitors for anonymous users. Anonymous users would just see "All Systems Operational" and everything else you do with the status page excluding the monitors/groups.
2. Have the possibility to set "anonymous friendly names". The logged-in friendly-name may be secret-foo-server, the anonymous friendly name may be Server 1.

❓ Alternatives

Currently you could set anonymized friendly names such as server 1 & server 2, but still you divulge the information that you have two servers. You would have to completely anonymize everything like so:

• Group: Frontend
  • Monitor: System 1
  • Monitor: System 2
  • Monitor: System 3
• Group: Backend
  • Monitor: System 1
  • Monitor: System 2
  • Monitor: System 3

Unfortunately this would mean that you would have multiple monitors for the same system (e.g. our secret-foo-server.domain.local once as is, and once as "Backend/System 1").

📝 Additional Context

No response

[chakflying]

Interesting. I guess an easy solution would be to add a checkbox to hide a monitor when you add them to the status page.

[OryonMax]

+1

[f1mishutka]

+1

Would like to show our customers our uptime statistics using nice Kuma!

[black23]

+1

[mondychan]

+1