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.

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

Wrong number of TCP connections reported in the details pane #378

Closed
2opremio opened this issue Aug 19, 2015 · 7 comments
Closed

Wrong number of TCP connections reported in the details pane #378

2opremio opened this issue Aug 19, 2015 · 7 comments
Assignees
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Milestone

Comments

@2opremio
Copy link
Contributor

The details pane of the scope container reads TCP connections 1:

screen shot 2015-08-19 at 6 29 00 pm

But the number of connections is clearly higher than 1:

screen shot 2015-08-19 at 6 30 52 pm

@peterbourgon
Copy link
Contributor

@2opremio is this still happening?

@2opremio
Copy link
Contributor Author

@peterbourgon I need to check but I won't have time to do this today. Can it wait until Monday?

@peterbourgon
Copy link
Contributor

No rush, was just doing some issue cleanup.

@2opremio
Copy link
Contributor Author

Yes, this is still broken. In the case below I think it breaks because of the reverse DNS lookup (leading to the same dataproducer.weave.local name from different IPs):
screen shot 2015-09-21 at 13 06 33

Here's the output of /api/report/: https://gist.github.com/2opremio/4aa41b303862270dad6e

I suspect it still breaks when no DNS records are involved. I will try to reproduce that too.

@2opremio
Copy link
Contributor Author

Here is another example with different DNS records:

screen shot 2015-09-21 at 13 22 50

Report: https://gist.github.com/2opremio/d6f78a62b84a7b4f8259

As I understand it, the count should be 4, and not 2.

Also, this example partly shows the problem with reverse DNS records pointed out at #504 (the view shows scope.weave.local names mixed up with ip-172-31-* names)

@2opremio
Copy link
Contributor Author

2opremio commented Oct 1, 2015

Here's another example:

screen shot 2015-10-01 at 2 05 41 pm

report: https://gist.github.com/2opremio/65d1858fa30a1bf0ec91

@tomwilkie tomwilkie added the bug Broken end user or developer functionality; not working as the developers intended it label Nov 5, 2015
@tomwilkie tomwilkie added this to the 0.12.0 milestone Dec 10, 2015
@tomwilkie tomwilkie modified the milestones: 0.13.0, 0.12.0 Jan 19, 2016
@paulbellamy
Copy link
Contributor

We don't show this anymore, so won't be an issue until #680 is done.

@paulbellamy paulbellamy removed this from the 0.13.0 milestone Feb 12, 2016
@tomwilkie tomwilkie self-assigned this Feb 23, 2016
@tomwilkie tomwilkie added this to the 0.13.0 milestone Feb 25, 2016
@davkal davkal modified the milestones: 0.14.0, 0.13.0 Feb 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Projects
None yet
Development

No branches or pull requests

5 participants