Improve resolution notification with some additional information #1313

Closed
opened 2026-02-28 02:17:04 -05:00 by deekerman · 10 comments
Owner

Originally created by @mabed-fr on GitHub (Aug 4, 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, Other

🔖 Feature description

Improve resolution notification with some additional information:

  • DOWN DATE
  • DATE OF UP(ALREADY PRESENT)
  • TOTAL DOWN DURATION

✔️ Solution

Improve resolution notification with some additional information:

  • DOWN DATE
  • DATE OF UP(ALREADY PRESENT)
  • TOTAL DOWN DURATION

Alternatives

NC

📝 Additional Context

NC

Originally created by @mabed-fr on GitHub (Aug 4, 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, Other ### 🔖 Feature description Improve resolution notification with some additional information: - DOWN DATE - DATE OF UP(ALREADY PRESENT) - TOTAL DOWN DURATION ### ✔️ Solution Improve resolution notification with some additional information: - DOWN DATE - DATE OF UP(ALREADY PRESENT) - TOTAL DOWN DURATION ### ❓ Alternatives NC ### 📝 Additional Context NC
deekerman 2026-02-28 02:17:04 -05:00
Author
Owner

@lazyjeffllc commented on GitHub (Jan 6, 2023):

Forgive my ignorance, how does this feature request get performed? We just wait for someone to work it or does louislam have to add this feature?

@lazyjeffllc commented on GitHub (Jan 6, 2023): Forgive my ignorance, how does this feature request get performed? We just wait for someone to work it or does louislam have to add this feature?
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

@EdyDeveloper commented on GitHub (May 28, 2023):

Bump
This would be awesome. It would allow me to stop using HetrixTools entirely. It's really handy to have all this info so that you don't have to do a bunch of math in your head, especially when you have lots of monitored services.

@EdyDeveloper commented on GitHub (May 28, 2023): Bump This would be awesome. It would allow me to stop using HetrixTools entirely. It's really handy to have all this info so that you don't have to do a bunch of math in your head, especially when you have lots of monitored services.
Author
Owner

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

@honestlai @EdyDeveloper
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 28, 2023): @honestlai @EdyDeveloper 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 28, 2023):

@mabed-fr
What exactly is your feature request?
Is this a duplicate of Templating (#975) or #2362?
If it is not, please edit your issue to make it more clear ^^

@CommanderStorm commented on GitHub (May 28, 2023): @mabed-fr What exactly is your feature request? Is this a duplicate of Templating (#975) or #2362? If it is not, please edit your issue to make it more clear ^^
Author
Owner

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

@lazyjeffllc

Forgive my ignorance, how does this feature request get performed? We just wait for someone to work it or does louislam have to add this feature?

The Contribution guide is at https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

@CommanderStorm commented on GitHub (May 28, 2023): @lazyjeffllc > Forgive my ignorance, how does this feature request get performed? We just wait for someone to work it or does louislam have to add this feature? The Contribution guide is at https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md
Author
Owner

@mabed-fr commented on GitHub (May 28, 2023):

Yes these are the same features, but none are started. Unfortunately I don't have the required skills. I can only be useful for the system network and DevOps side

@mabed-fr commented on GitHub (May 28, 2023): Yes these are the same features, but none are started. Unfortunately I don't have the required skills. I can only be useful for the system network and DevOps side
Author
Owner

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

Yes these are the same features

Please close this PR then 😉
Duplicates just make managing issues harder

none are started.

My plan to improve upon this state is:

  • reformat the monitors see PR #3182
  • make sure that all notification providers code looks similar (see zoho-cliq vs telegram for what I mean)
  • fix that some monitors handle down/up vs general notifications differently
  • after upon improving on the code quality in this area, these features will be easier

I can only be useful for the system network and DevOps side

As mentioned in #1349, this project was lacking in this department. In the past year, it got better a lot, but we are not quite in a place I would call happy.
Louis seems to like manual processes for release management (see https://github.com/louislam/uptime-kuma/pull/213), but all testing PRs have been accepting ⇒ A PR adding more (unit)tests would likely be accepted and improve future reviews.
Also note #2720

@CommanderStorm commented on GitHub (May 28, 2023): > Yes these are the same features Please close this PR then 😉 Duplicates just make managing issues harder > none are started. My plan to improve upon this state is: - reformat the monitors see PR #3182 - make sure that all notification providers code looks similar (see [zoho-cliq](https://github.com/louislam/uptime-kuma/blob/master/server/notification-providers/zoho-cliq.js) vs [telegram](https://github.com/louislam/uptime-kuma/blob/master/server/notification-providers/telegram.js) for what I mean) - fix that some monitors handle down/up vs general notifications differently - after upon improving on the code quality in this area, these features will be easier >I can only be useful for the system network and DevOps side As mentioned in #1349, this project was lacking in this department. In the past year, it got better a lot, but we are not quite in a place I would call happy. Louis seems to like manual processes for release management (see https://github.com/louislam/uptime-kuma/pull/213), but all testing PRs have been accepting ⇒ A PR adding more (unit)tests would likely be accepted and improve future reviews. Also note #2720
Author
Owner

@CommanderStorm commented on GitHub (Aug 31, 2023):

Yes these are the same features

@mabed-fr ?

Please also note more specific issues like https://github.com/louislam/uptime-kuma/issues/2362 which will be resolved in https://github.com/louislam/uptime-kuma/pull/3394

@CommanderStorm commented on GitHub (Aug 31, 2023): > Yes these are the same features @mabed-fr ? Please also note more specific issues like https://github.com/louislam/uptime-kuma/issues/2362 which will be resolved in https://github.com/louislam/uptime-kuma/pull/3394
Author
Owner

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

Yes these are the same features

Closing as a duplicate as discussed above

@CommanderStorm commented on GitHub (Dec 6, 2023): > Yes these are the same features Closing as a duplicate as discussed above
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#1313
No description provided.