Summary graph / stats page for all targets?

[luckman212]

Hello, sorry for posting this as an issue. I tried searching the docs/FAQ and other open issues before creating this to avoid a duplicate question.

I'm wondering if it's possible to have a view in Trippy that shows RTT stats and perhaps a small graph of the final hop for all active targets. I frequently test latency to a fixed set of hosts and find myself needing to flip through them quickly to get an overview of connectivity- when what I would prefer to see is a view of the stats for all targets on one screen.

(thank you for this wonderful tool)

[fujiapple852]

Hi @luckman212 and thanks for the suggestion.

Hello, sorry for posting this as an issue. I tried searching the docs/FAQ and other open issues before creating this to avoid a duplicate question.

Perfectly fine to raise here or on zulip/matrix chat.

a view in Trippy that shows RTT stats and perhaps a small graph of the final hop for all active targets
To check I understand correctly, when you say "all active targets" I assume you are referring to running trippy against multiple targets at the same time, i.e. trip foo.com bar.com? And you would like a new screen that has a table (and/or chart) with a row per target (the target row) rather than a row per hop to a single target as it is today?

I have mixed feelings on this; it feels a little outside of the scope of Trippy, which is all about tracing the path to a target or targets. I wouldn't want the primary focus of Trippy to shift from a tracing tool to an endpoint latency monitoring tool.

On the other hand, Trippy does have all of data needed to do this and could provide this functionality which many people may find beneficial.

cc @c-git for an opinion.

[c-git]

I saw this and was tired up at the time and forgot to respond. I have a very similar need with the addition of storage of history and notifications. My current solution doesn't use trippy and doesn't meet all my needs. It only does notifications and only runs on Linux.

I'm currently using https://github.com/rust-practice/conn_mon

I think especially given that trippy has been refactored to separate out the core we could do something on top of trippy and depending on how that works out we could move the most appropriate parts into trippy after careful consideration for fit. I'd love to give it a try but know I don't have the time to spare right now.