mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Improve resolution notification with some additional information #1313
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#1313
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 @mabed-fr on GitHub (Aug 4, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
New Notification, Other
🔖 Feature description
Improve resolution notification with some additional information:
✔️ Solution
Improve resolution notification with some additional information:
❓ Alternatives
NC
📝 Additional Context
NC
@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?
@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
@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.
@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):
@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):
@lazyjeffllc
The Contribution guide is at https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md
@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
@CommanderStorm commented on GitHub (May 28, 2023):
Please close this PR then 😉
Duplicates just make managing issues harder
My plan to improve upon this state is:
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 (Aug 31, 2023):
@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 (Dec 6, 2023):
Closing as a duplicate as discussed above