Skip to content
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.

Sign up for GitHub

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

Jump to bottom

show me the connections! #1713

Closed
rade opened this issue Jul 21, 2016 · 3 comments
Closed

show me the connections! #1713

rade opened this issue Jul 21, 2016 · 3 comments
Assignees
@rade
Labels
feature Indicates that issue is related to new end user functionality
Milestone
1.0.0 (kubecon)

Comments

@rade
Copy link
Member

rade commented Jul 21, 2016

Scope collects heaps of information about connections, and uses it to lay out the topology graphs, yet it is remarkably difficult to actually get hold of even the most basic details of these connections. For example, I frequently find myself wondering "Why is my container X talking to the Internet? It shouldn't! What is it talking to?"

  • clicking on the edge between my container and the "Internet (outbound)" node does precisely nothing. That would be the most obvious place to show connection information. See make topology view edges more useful #1636
  • clicking on the node for my container brings up the details panel, with lovely lists of inbound and outbound connections... but this just gives me node names, ports and connection counts, not IP addresses or DNS names. So in case of outbound connections to the Internet, I am just being told that there 37 connections to the Internet on port 443. Marvellous.
  • clicking on the "Internet (outbound)" node does show me IP addresses / DNS names for all the outbound connection destinations; but this is for all containers, so to find the connections for my container I have to search for my container name in a long list that isn't searchable and has the name truncated.
@rade rade added the feature Indicates that issue is related to new end user functionality label Jul 21, 2016
@mjlodge
Copy link

mjlodge commented Jul 21, 2016

MTU for an interface would also be good to know when troubleshooting...

@hamid-elaosta
Copy link

Agreed, I'm looking at scope right now for a set of microservices one of which should absolutely not be connecting to the internet, It's possible it's not since it's communicating with a service outside of a container, but I can't confirm this from the information available.

@rade rade modified the milestone: September2016 Aug 17, 2016
@rade rade self-assigned this Sep 19, 2016
@rade rade modified the milestones: 0.18/1.0, October2016 Sep 19, 2016
rade added a commit that referenced this issue Sep 19, 2016
@rade
show more details of a node's internet connections
bcf21b1 
in the details panel, instead of showing connections to/from the
internet as "TheInternet <port>", we now show "<dns-name>(<ip_addr>)
<port>" (or just "<ip_addr> <port>" if we don't have a dns name).

Fixes #1713.
@rade rade mentioned this issue Sep 19, 2016
Merged
rade added a commit that referenced this issue Sep 19, 2016
@rade
Merge pull request #1875 from weaveworks/1713-show-internet-connections
d008919 
show more details of a node's internet connections

Fixes #1713.
@rade
Copy link
Member Author

rade commented Sep 19, 2016

I've added more details for Internet connections in #1875.

More fine-grained info, e.g. source IPs, IPs for connections to/from non-Internet nodes, MTUs, etc are part of #801.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rade rade

Labels
feature Indicates that issue is related to new end user functionality
Projects
None yet
Milestone
1.0.0 (kubecon)
Development

No branches or pull requests
3 participants
@rade @mjlodge @hamid-elaosta