Potential use cases:

• Create an HTTPS monitor for https://www.github.com but make the clickable link take you to https://www.githubstatus.com
• Create an HTTPS monitor for https://www.icloud.com/ but make the clickable link take you to https://www.apple.com/support/systemstatus/

Often I want to set the monitoring url to example.com/health or some service specific health status page that intended for monitoring.
However it would be nice if the the clickable url could direct to a different page, such as the main site.

Several atlassian and gitlab services, I am hitting an API to make sure the internal status items are loading (Instead of just getting a SAML/SSO page on the HTTP request).

I would love it so I could make these a link where an end user click it, and it goes to the actual service, not the API endpoint.

It would be extremely useful if this were also available for groups, so that a clickable link can be provided against group monitors.

It would be extremely useful if this were also available for groups, so that a clickable link can be provided against group monitors.

I was about to submit the same request before I found this request.

My use case is a server with about 50 containers, and I have them organized into groups displayed on my main status page, and would like the group name to be a link to another status page showing the individual services in the group.

I have some services locked behind Authentik on the public URL, and have linked my services to Uptime Kuma using the internal IP and port to get accurate results.

The downside is that the clickable URL option is now off the table, as it shares the internal URL. Being able to change this would be HUGE, and really appreciated!

My use case is that I have a lot of monitors. So with the groups feature, I could create a status page with just the groups as a service and when clicking it would take me to the status page with the services of that group.

My use case is that I have a lot of monitors. So with the groups feature, I could create a status page with just the groups as a service and when clicking it would take me to the status page with the services of that group.

Here's a BIG workaround for you based on how I understand the implementation described. I just tested this:

1. Create your new group status page. Copy the URL.
2. Create a new HTTP monitor. Put in the URL for your new status page from step 1. Name the monitor the group name you want. Save it and verify it's monitoring that URL.
3. Change the monitor type from HTTP to Group.
4. Now add your other monitors to the group.
5. Add this new group to a status page and enable the URL. It will use the status page URL from step 1.

The trick is that once you put in the URL for the http/s monitor, it will use it in the status page link even when you change the monitor type from http/s to group.

It's pretty static. I can't imagine a way to change the URL once you've converted the monitor to a group.

That is a pretty creative abuse of said bug.
The reason this exists/"works" is that the monitoring data is not wiped on switching to another monitoring type and the frontend likely ony checks that the url exists.

Can work on it. Just a question: is it okay if the link is monitor-related or does it need to be depending of each status page?

Also @CommanderStorm, is it okay if I create this feature for UK 1.X ?

We won't add features to 1.x.
Only critical bugs or security issues.