mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Make elapsed time formatting show more accurate information when heartbeats happened #4548
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#4548
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zeshinsei on GitHub (Dec 24, 2025).
⚠️ Please verify that your question has not already been reported
🛡️ Security Policy
📝 Describe your problem
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
@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:
Feedback, mockups, or contributions are always welcome.
@eureka928 commented on GitHub (Jan 15, 2026):
@CommanderStorm Is this fixed?
If not, I'd like to take over
@CommanderStorm commented on GitHub (Jan 15, 2026):
I don't think this is fixed.