Send alert if ping is >X ms #1931

Closed
opened 2026-02-28 02:37:32 -05:00 by deekerman · 6 comments
Owner

Originally created by @mjalindahl on GitHub (Feb 23, 2023).

⚠️ 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

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

Originally created by @mjalindahl on GitHub (Feb 23, 2023). ### ⚠️ 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 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_
deekerman 2026-02-28 02:37:32 -05:00
Author
Owner

@mtelgkamp commented on GitHub (Feb 24, 2023):

Sounds similar to https://github.com/louislam/uptime-kuma/issues/2754, maybe a duplicate?

@mtelgkamp commented on GitHub (Feb 24, 2023): Sounds similar to https://github.com/louislam/uptime-kuma/issues/2754, maybe a duplicate?
Author
Owner

@nmcc1212 commented on GitHub (Mar 24, 2023):

also #1813 and the original seems to be #459

@nmcc1212 commented on GitHub (Mar 24, 2023): also #1813 and the original seems to be #459
Author
Owner

@nmcc1212 commented on GitHub (Mar 24, 2023):

And an active PR #1878

@nmcc1212 commented on GitHub (Mar 24, 2023): And an active PR #1878
Author
Owner

@Natgho commented on GitHub (May 9, 2023):

@louislam @Saibamen please take a look at this . It is important.

@Natgho commented on GitHub (May 9, 2023): @louislam @Saibamen please take a look at this . It is important.
Author
Owner

@nmcc1212 commented on GitHub (May 9, 2023):

@Natgho dont use this issue. it is a duplicate. use one of the issues i linked above

@nmcc1212 commented on GitHub (May 9, 2023): @Natgho dont use this issue. it is a duplicate. use one of the issues i linked above
Author
Owner

@louislam commented on GitHub (May 9, 2023):

Duplicate of #1813

@louislam commented on GitHub (May 9, 2023): Duplicate of #1813
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#1931
No description provided.