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
Thanks for a great tool! I put a few different gping instances inside tmux panes, and it'd be convenient to have each of them with the same relative scale when being rendered inside a more densely populated "dashboard-style" window. So if one of the hosts became slow, which led to a ping latency, the --minimum-latency 300, e.g., would sort of have the necessary "graph slack" to eat the higher ping times and keep all windows graphs at the same local maximum latency/y-axis. This would allow for easier user scanning looking for anomalies.
I'm not partial to that parameter name, I just would appreciate the functionality. If the feature isn't in scope of the project, please just close the request, no problem. Thanks again for a useful tool 👍
The text was updated successfully, but these errors were encountered:
Thanks for a great tool! I put a few different
gping
instances insidetmux
panes, and it'd be convenient to have each of them with the same relative scale when being rendered inside a more densely populated "dashboard-style" window. So if one of the hosts became slow, which led to a ping latency, the--minimum-latency 300
, e.g., would sort of have the necessary "graph slack" to eat the higher ping times and keep all windows graphs at the same local maximum latency/y-axis. This would allow for easier user scanning looking for anomalies.I'm not partial to that parameter name, I just would appreciate the functionality. If the feature isn't in scope of the project, please just close the request, no problem. Thanks again for a useful tool 👍
The text was updated successfully, but these errors were encountered: