Downtime Duration in the Notification #773

New issue

Closed

opened 2026-02-28 01:57:30 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 01:57:30 -05:00

Owner

Originally created by @sanjue007 on GitHub (Jan 24, 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

Please add Downtime duration in the Notification body

(Name) is now UP
Downtime: 2 min
Target: (IP address)[ping]
Noticed at: 2022-01-24 07:53:37 (UTC+00:00)

✔️ Solution

Please add Downtime duration in the Notification body

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @sanjue007 on GitHub (Jan 24, 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 Please add Downtime duration in the Notification body (Name) is now UP **Downtime: 2 min** Target: (IP address)[ping] Noticed at: 2022-01-24 07:53:37 (UTC+00:00) ### ✔️ Solution Please add Downtime duration in the Notification body ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 01:57:30 -05:00

closed this issue
added the
feature-request

A:monitor

A:notifications
labels

deekerman commented

2026-02-28 01:57:36 -05:00

Author

Owner

@koen20 commented on GitHub (Jan 24, 2022):

Duplicate of #177 and #428

@koen20 commented on GitHub (Jan 24, 2022): Duplicate of #177 and #428

deekerman commented

2026-02-28 01:57:37 -05:00

Author

Owner

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

@sanjue007
I think this is a duplicate of #177 (which has #428 as a duplicate)
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

@CommanderStorm commented on GitHub (Jul 25, 2023): @sanjue007 I think this is a duplicate of #177 (which has #428 as a duplicate) If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage? If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

deekerman commented

2026-02-28 01:57:37 -05:00

Author

Owner

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

Duplicate of #177

@CommanderStorm commented on GitHub (Dec 13, 2023): Duplicate of #177