You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My network provider is quite unstable, thanks to DSL (yes, still used in 2024 π)
Happens in about 1-2 weeks, and since home network is sometimes critical for communication I need to get notified before I notice problems while working.
Example use case:
ping to google.com jumps from 40-60ms to 120-200ms or even 300-500ms, which are the signs that something is wrong on ISP router side.
βοΈ Solution
Proposal:
Have additional category "Latency alert" (or some better naming, doesn't really matter), which would detect and notify about latency issues.
β Alternatives
The only option is to "suspect" and then "check", but it is reactive behaviour which I can do by running mtr (or WinMTR) to check path ping.
I would really love to be notified proactively about problem.
π Additional Context
No response
The text was updated successfully, but these errors were encountered:
π I have found these related issues/pull requests
π·οΈ Feature Request Type
New notification-provider, Other
π Feature description
My network provider is quite unstable, thanks to DSL (yes, still used in 2024 π)
Happens in about 1-2 weeks, and since home network is sometimes critical for communication I need to get notified before I notice problems while working.
Example use case:
ping to google.com jumps from 40-60ms to 120-200ms or even 300-500ms, which are the signs that something is wrong on ISP router side.
βοΈ Solution
Proposal:
Have additional category "Latency alert" (or some better naming, doesn't really matter), which would detect and notify about latency issues.
β Alternatives
The only option is to "suspect" and then "check", but it is reactive behaviour which I can do by running mtr (or WinMTR) to check path ping.
I would really love to be notified proactively about problem.
π Additional Context
No response
The text was updated successfully, but these errors were encountered: