mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
show minutes a service is down #734
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#734
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 @robkooper on GitHub (Jan 9, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
Other
🔖 Feature description
Right now it will show me the date and time when a service goes down and when it comes back up. It would be nice to also show how long it was down for in the notifications. This comes really hand if a lot of services go down (reboot) and come back up. This way I don't have to try and find different notifications to see how long a service was down for.
✔️ Solution
As part of the notification say:
[✅ Up] 200 - OK, it was down for 4 minutes and 3 seconds
❓ Alternatives
No response
📝 Additional Context
No response
@csjoh commented on GitHub (Jan 22, 2022):
+1 for this.
It would also be nice to show the amount of time the service was down in the dashboard.
@gavinsauder commented on GitHub (May 12, 2022):
+1 for this.
@feriahmad commented on GitHub (Feb 2, 2023):
+1 for this
@rpgscience commented on GitHub (Mar 27, 2023):
+1 for this
@CommanderStorm commented on GitHub (Dec 13, 2023):
Duplicate of #177 => closing and continuing to track there