-
Notifications
You must be signed in to change notification settings - Fork 712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it clear which nodes have incoming connections and which nodes have outgoing connections when you have a node selected #875
Comments
If you combine this with some kind of semantic colouring, this might be interesting way to answer the question "why is this container sick". What do you think @davkal @foot @paulbellamy? |
I would be more in favour of this if "incoming" vs "outgoing" was more than a guess, but even determining what that means is tricky. |
conntrack'd connections have direction: #539 |
I like it, though arrow offset will have to be calculated differently for all new shapes. |
This also came up with Darren from Rancher. |
But most connections are not conntrack'd (only short-lived ones are), no? |
Actually almost all connections are conntracked, the set of ones detected On Monday, 15 February 2016, Paul Bellamy notifications@github.com wrote:
|
Edge direction is now even more meaningful: we get them from conntrack. @davkal do you think this is something we could have a go at (even without arrow heads)? |
+1 for adding a visual indicator for direction, to edges. #872 |
How is this different from #872? |
This is talking about the "selected" mode, where as #872 is in the general canvas. Also this suggestion is about changing the location of the nodes (incoming at the top, outgoing at the bottom) when you select a node, whereas #872 is just about adding a direction indicator for edges on canvas. |
I like that, and it's something that could be done independently from tackling the thorny/controversial issue of adding arrow heads. |
Related to #1636 |
This is mostly accomplished by #2317. Concepts involving re-arranging the nodes were unsuccessful, as it lead to very unbalanced "sides" of the diagram which lead to difficult to read diagrams. Closing. |
Something like this (when viewing the detail panel):
I think this will make it super obvious what containers / process etc something is talking to, and what container / process is talking to it.
The text was updated successfully, but these errors were encountered: