You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I could not find related items to this. I assume most users just use the landing page of systems being monitored, or they are looking at other things, like API endpoints, TCP ports etc.
🏷️ Feature Request Type
Status-page
🔖 Feature description
Well designed applications typically provide a special endpoint that can be used to check the health status of the application.
However, when you utilize such and endpoint as the heart beat URL configured in a monitor, and the configure the status page to expose a link to the service being monitored, the link will just go to the health check URL.
This is typically not very useful for "normal" users, who most likely expected to see the applications landing page, instead of some JSON/plaintext diagnostic output.
It would be, I think, useful to allow an admin to (optionally) specify, at the very least, a different path for the generated service link on the status page.
✔️ Solution
When configuring a monitor on the status page, in addition to the "Show Clickable Link" check box, add an UI element to (optionally) provide an alternative path for the generated clickable link.
This could be, for example, a text input, labeled "Alternative path", where
no input signifies "behavior as current - use configured monitor URL"
/ indicate the link should go to the root
/home indicates the link should go to root+/home
To illustrate, say the the configured monitor has a link of https://abs.home/ping
Currently, if the monitor is made clickable on the status page, the browser will open https://abs.home/ping.
A normal user that has access to the status page most likely would prefer to have been take to https://abs.home/
In order to fascinate this, imagine the textbox as described above was available to the status page creator.
They could then have entered into that box the the value /, which would then result in the "better" user experience - i.e. the user is take to https://abs.home/
❓ Alternatives
One obvious alternative is to leave functionality as is. The status-page is still very usable for persons concerned with tracking uptime.
The configuration could also be made available in the monitor itself, however I feel that mixes unrelated concerns (function vs presentation vs user UX)
📝 Additional Context
No response
The text was updated successfully, but these errors were encountered:
📑 I have found these related issues/pull requests
I could not find related items to this. I assume most users just use the landing page of systems being monitored, or they are looking at other things, like API endpoints, TCP ports etc.
🏷️ Feature Request Type
Status-page
🔖 Feature description
Well designed applications typically provide a special endpoint that can be used to check the health status of the application.
However, when you utilize such and endpoint as the heart beat URL configured in a monitor, and the configure the status page to expose a link to the service being monitored, the link will just go to the health check URL.
This is typically not very useful for "normal" users, who most likely expected to see the applications landing page, instead of some JSON/plaintext diagnostic output.
It would be, I think, useful to allow an admin to (optionally) specify, at the very least, a different path for the generated service link on the status page.
✔️ Solution
When configuring a monitor on the status page, in addition to the "Show Clickable Link" check box, add an UI element to (optionally) provide an alternative path for the generated clickable link.
This could be, for example, a text input, labeled "Alternative path", where
/
indicate the link should go to theroot
/home
indicates the link should go toroot+/home
To illustrate, say the the configured monitor has a link of
https://abs.home/ping
Currently, if the monitor is made clickable on the status page, the browser will open
https://abs.home/ping
.A normal user that has access to the status page most likely would prefer to have been take to
https://abs.home/
In order to fascinate this, imagine the textbox as described above was available to the status page creator.
They could then have entered into that box the the value
/
, which would then result in the "better" user experience - i.e. the user is take tohttps://abs.home/
❓ Alternatives
One obvious alternative is to leave functionality as is. The status-page is still very usable for persons concerned with tracking uptime.
The configuration could also be made available in the monitor itself, however I feel that mixes unrelated concerns (function vs presentation vs user UX)
📝 Additional Context
No response
The text was updated successfully, but these errors were encountered: