mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Add how long was down, when sending up notification. #1596
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#1596
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 @ForceConstant on GitHub (Dec 1, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
New Notification
🔖 Feature description
It would be useful for me that when a service goes down, and then comes back up, that the notification says how long it was down for.
✔️ Solution
Notification would look like:
[Service] [Up] Was down for 3:12 minutes.
❓ Alternatives
No response
📝 Additional Context
No response
@ramyelgenany commented on GitHub (Mar 4, 2023):
I really need this and will be very helpful
@honestlai commented on GitHub (May 24, 2023):
Bump
Would love to have this as well, it's the only reason I haven't moved off of UpTimeRobot
@CommanderStorm commented on GitHub (May 25, 2023):
@ramymoh @honestlai
Please refrain from posting
+1/ requests for updates things on issues, as this makes issue-management harder.Issues are for discussing what needs to be done how by whom.
We use 👍🏻 on issues to prioritise work.
@CommanderStorm commented on GitHub (May 25, 2023):
Related to #975
@CommanderStorm commented on GitHub (Dec 13, 2023):
Duplicate of #177 => closing and continuing to track there