mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Notify about slow response time #1196
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#1196
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 @pemassi on GitHub (Jun 22, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
New Notification
🔖 Feature description
Seems like Uptime Kuma now has a lot of monitoring types and notifies certificate expiring warning, not only service down.
I think notifying that response time is slow(or high) might be good feature for next step.
✔️ Solution
Since, Uptime Kuma already logging response time into the database, we can use that data for this feature.
❓ Alternatives
No response
📝 Additional Context
No response
@davidus05 commented on GitHub (Jun 22, 2022):
I'd rename that issue, as the title is a bit misleading.
Better: "New monitor: Notify about slow response time"
But, nevertheless +1 from me
@pemassi commented on GitHub (Jun 22, 2022):
I've renamed it! Thx!
@mtelgkamp commented on GitHub (Sep 9, 2022):
I think this is a duplicate of #459