Add how long was down, when sending up notification. #1596

Closed
opened 2026-02-28 02:26:35 -05:00 by deekerman · 5 comments
Owner

Originally created by @ForceConstant on GitHub (Dec 1, 2022).

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ 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

Originally created by @ForceConstant on GitHub (Dec 1, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ 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_
Author
Owner

@ramyelgenany commented on GitHub (Mar 4, 2023):

I really need this and will be very helpful

@ramyelgenany commented on GitHub (Mar 4, 2023): I really need this and will be very helpful
Author
Owner

@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

@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
Author
Owner

@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): @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](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc).
Author
Owner

@CommanderStorm commented on GitHub (May 25, 2023):

Related to #975

@CommanderStorm commented on GitHub (May 25, 2023): Related to #975
Author
Owner

@CommanderStorm commented on GitHub (Dec 13, 2023):

Duplicate of #177 => closing and continuing to track there

@CommanderStorm commented on GitHub (Dec 13, 2023): Duplicate of #177 => closing and continuing to track there
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#1596
No description provided.