mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Total Time for outage #2295
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#2295
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 @thekayman on GitHub (Jun 21, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
New Notification, UI Feature
🔖 Feature description
Hi, is it possible to add into the notification and UI how long a monitor was down for.
✔️ Solution
It would be great if within the notification and UI when a monitor goes down and comes back up it shows how long the outage was for.
i.e. ([Monitor Name] [✅ Up] 200 - OK Time (UTC): 2023-06-22 02:42:48.611 (Down for 2 mins 10 seconds)
and in the UI something similar.
❓ Alternatives
No response
📝 Additional Context
No response
@prabhsharan36 commented on GitHub (Jul 9, 2023):
@louislam should I work on this feature? This looks like a valid and useful feature request.
@CommanderStorm commented on GitHub (Jul 9, 2023):
PRs welcome, as always.
If you do decide to work on this, please break this into multiple parts for easier reviewability:
@CommanderStorm commented on GitHub (Dec 13, 2023):
Duplicate of #177 => closing and continuing to track there