-
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
Wrong number of TCP connections reported in the details pane #378
Comments
@2opremio is this still happening? |
@peterbourgon I need to check but I won't have time to do this today. Can it wait until Monday? |
No rush, was just doing some issue cleanup. |
Yes, this is still broken. In the case below I think it breaks because of the reverse DNS lookup (leading to the same Here's the output of I suspect it still breaks when no DNS records are involved. I will try to reproduce that too. |
Here is another example with different DNS records: 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 |
Here's another example: report: https://gist.github.com/2opremio/65d1858fa30a1bf0ec91 |
We don't show this anymore, so won't be an issue until #680 is done. |
The details pane of the scope container reads TCP connections 1:
But the number of connections is clearly higher than 1:
The text was updated successfully, but these errors were encountered: