How long host was down in notification #1949

Closed
opened 2026-02-28 02:38:10 -05:00 by deekerman · 6 comments
Owner

Originally created by @sibberio on GitHub (Feb 27, 2023).

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

I would like to know how long an host was down when I receive the notification that it’s up again

✔️ Solution

Add in the notification the downtime

Alternatives

No response

📝 Additional Context

No response

Originally created by @sibberio on GitHub (Feb 27, 2023). ### ⚠️ 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 I would like to know how long an host was down when I receive the notification that it’s up again ### ✔️ Solution Add in the notification the downtime ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_
Author
Owner

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

I really hope it can be added also I'm only receiving when host is down, never receive notifications when it's up again.

@ramyelgenany commented on GitHub (Mar 4, 2023): I really hope it can be added also I'm only receiving when host is down, never receive notifications when it's up again.
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 27, 2023):

@ramymoh please open another ticket in the help category.
This is not the corrrect issue to discuss this.

@CommanderStorm commented on GitHub (May 27, 2023): @ramymoh please open another ticket in the `help` category. This is not the corrrect issue to discuss this.
Author
Owner

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

@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 27, 2023): @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 27, 2023):

Related to this issue is the ability to format messages send.

@CommanderStorm commented on GitHub (May 27, 2023): Related to this issue is the ability to format messages send. - #1529 - #2661 - https://github.com/louislam/uptime-kuma/issues/2617 - https://github.com/louislam/uptime-kuma/issues/2387 - and more: see #646 for a deeper discussion
Author
Owner

@CommanderStorm commented on GitHub (Mar 25, 2025):

noticed this is a duplicate of https://github.com/louislam/uptime-kuma/issues/177

@CommanderStorm commented on GitHub (Mar 25, 2025): noticed this is a duplicate of https://github.com/louislam/uptime-kuma/issues/177
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#1949
No description provided.