status page: normalize push monitor #4643

New issue

Closed

opened 2026-02-28 04:10:16 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 04:10:16 -05:00

Owner

Originally created by @cachho on GitHub (Jan 26, 2026).

search for is:issue push monitor status page gave no meaningful results from what I could find.

somewhat related to #1888 in theory, although this is coming from a different problem.

🔖 Feature description

I'm not sure if normalize is the right term, please correct.

I'm using a push monitor on registration. I want to publicly report the status of the registration by including it on a uptime-kuma status page.

The problem is that it shows the timestamp for every single sign-up and thus my user numbers become public.

Another issue with this is that the beats are not evenly spaced for push monitors, e.g. in this example, the left and the middle are both 18 hours ago when users would expect it to be 9h.

This would also be solved with a feature like this.

✔️ Solution

To normalize the push monitor specifically on the status page, it could be normalized to show a "beat" for instance for every full hour, where it look at the most recent status at this point in time and displays it as such.

There could be a setting to configure the time frame.

❓ Alternatives

I love push monitors, it works really well, but at the end of the day, what's useful for me might not be the information I'm trying to convey to my users.

📝 Additional Context

Version 2.0.1

Originally created by @cachho on GitHub (Jan 26, 2026). ### 📑 I have found these related issues/pull requests search for `is:issue push monitor status page` gave no meaningful results from what I could find. somewhat related to #1888 in theory, although this is coming from a different problem. ### 🔖 Feature description I'm not sure if normalize is the right term, please correct. I'm using a push monitor on registration. I want to publicly report the status of the registration by including it on a uptime-kuma status page. The problem is that it shows the timestamp for every single sign-up and thus my user numbers become public. Another issue with this is that the beats are not evenly spaced for push monitors, e.g. in this example, the left and the middle are both 18 hours ago when users would expect it to be 9h. <img width="980" height="154" alt="Image" src="https://github.com/user-attachments/assets/c848bd90-8b8f-4503-972b-584a3e8d420e" /> This would also be solved with a feature like this. ### ✔️ Solution To normalize the push monitor specifically on the status page, it could be normalized to show a "beat" for instance for every full hour, where it look at the most recent status at this point in time and displays it as such. There could be a setting to configure the time frame. ### ❓ Alternatives I love push monitors, it works really well, but at the end of the day, what's useful for me might not be the information I'm trying to convey to my users. ### 📝 Additional Context Version 2.0.1