Make elapsed time formatting show more accurate information when heartbeats happened #4548

Open
opened 2026-02-28 04:06:58 -05:00 by deekerman · 3 comments
Owner

Originally created by @zeshinsei on GitHub (Dec 24, 2025).

⚠️ Please verify that your question has not already been reported

🛡️ Security Policy

📝 Describe your problem

Image

The line for elapsed time is between 2:22pm and now (4:20pm), however it incorrectly says "1h" where it is essentially a representation of the last 2 hours. Additionally, the middle should have a label of "1h" or the sort.

Version: 2.0.2

📝 Error Message(s) or Log


🐻 Uptime-Kuma Version

2.0.2

💻 Operating System and Arch

Synology NAS, DSM 7.2.2-72806 Update 5

🌐 Browser

Firefox 146.0.1 (64-bit)

🖥️ Deployment Environment

Embedded SQL database

Container Manager v24.0.2-1543

Originally created by @zeshinsei on GitHub (Dec 24, 2025). ### ⚠️ Please verify that your question has not already been reported - [x] I have searched the [existing issues](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue%20sort%3Acreated-desc%20) and found no similar reports. ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Describe your problem <img width="1665" height="163" alt="Image" src="https://github.com/user-attachments/assets/727c7054-ca32-48b8-bd6c-a52b92e195b5" /> The line for elapsed time is between 2:22pm and now (4:20pm), however it incorrectly says "1h" where it is essentially a representation of the last 2 hours. Additionally, the middle should have a label of "1h" or the sort. Version: 2.0.2 ### 📝 Error Message(s) or Log ```bash session ``` ### 🐻 Uptime-Kuma Version 2.0.2 ### 💻 Operating System and Arch Synology NAS, DSM 7.2.2-72806 Update 5 ### 🌐 Browser Firefox 146.0.1 (64-bit) ### 🖥️ Deployment Environment Embedded SQL database Container Manager v24.0.2-1543
Author
Owner

@CommanderStorm commented on GitHub (Dec 24, 2025):

The time span shown isn’t exactly 2 hours. In your example, the left side represents about 1 hour and 58 minutes, so labeling it as "2h" wouldn’t be accurate. Adding intermediate markers (like a clear "1h" label) is also harder than it looks, especially when accounting for different screen sizes.

This area is entirely volunteer-driven, so I can’t promise that someone will be able to work on improving the elapsed-time display soon. One possible improvement could be to show more detail on hover (for example), which might reduce confusion without changing the layout.
Adding a minutes for this is also entirely possible.

We did improve time formatting in other parts of the app around the 2.1 release, and we’re gradually rolling those improvements out further. If you’re interested, feel free to give the current 2.1 beta a spin:

ghcr.io/louislam/uptime-kuma:2.1.0-beta.0

Feedback, mockups, or contributions are always welcome.

@CommanderStorm commented on GitHub (Dec 24, 2025): The time span shown isn’t exactly 2 hours. In your example, the left side represents about 1 hour and 58 minutes, so labeling it as "2h" wouldn’t be accurate. Adding intermediate markers (like a clear "1h" label) is also harder than it looks, especially when accounting for different screen sizes. This area is entirely volunteer-driven, so I can’t promise that someone will be able to work on improving the elapsed-time display soon. One possible improvement could be to show more detail on hover (for example), which might reduce confusion without changing the layout. Adding a minutes for this is also entirely possible. We did improve time formatting in other parts of the app around the 2.1 release, and we’re gradually rolling those improvements out further. If you’re interested, feel free to give the current 2.1 beta a spin: ``` ghcr.io/louislam/uptime-kuma:2.1.0-beta.0 ``` Feedback, mockups, or contributions are always welcome.
Author
Owner

@eureka928 commented on GitHub (Jan 15, 2026):

@CommanderStorm Is this fixed?
If not, I'd like to take over

@eureka928 commented on GitHub (Jan 15, 2026): @CommanderStorm Is this fixed? If not, I'd like to take over
Author
Owner

@CommanderStorm commented on GitHub (Jan 15, 2026):

I don't think this is fixed.

@CommanderStorm commented on GitHub (Jan 15, 2026): I don't think this is fixed.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#4548
No description provided.