mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Send alert if ping is >X ms #1931
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#1931
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 @mjalindahl on GitHub (Feb 23, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
New Notification
🔖 Feature description
Hi there, love UK. I have quite a few Sonos devices that I monitor via UK. But, anything over let's say 20ms, I consider that Sonos device to be "down." Having a really high ping time makes the Sonos not play nicely with the others.
✔️ Solution
So, since UK is already my centralized ping monitor, it would be nice to have a notification that alerts me if a device has a ping time of >X ms for Y seconds.
Thanks!
❓ Alternatives
No response
📝 Additional Context
No response
@mtelgkamp commented on GitHub (Feb 24, 2023):
Sounds similar to https://github.com/louislam/uptime-kuma/issues/2754, maybe a duplicate?
@nmcc1212 commented on GitHub (Mar 24, 2023):
also #1813 and the original seems to be #459
@nmcc1212 commented on GitHub (Mar 24, 2023):
And an active PR #1878
@Natgho commented on GitHub (May 9, 2023):
@louislam @Saibamen please take a look at this . It is important.
@nmcc1212 commented on GitHub (May 9, 2023):
@Natgho dont use this issue. it is a duplicate. use one of the issues i linked above
@louislam commented on GitHub (May 9, 2023):
Duplicate of #1813