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

TCP connections, bytes ingress/egress -- what do these mean? #151

Closed
squaremo opened this issue Jun 2, 2015 · 3 comments
Closed

TCP connections, bytes ingress/egress -- what do these mean? #151

squaremo opened this issue Jun 2, 2015 · 3 comments

Comments

@squaremo
Copy link

squaremo commented Jun 2, 2015

It's not clear what "TCP connections" corresponds to (sometimes it's in the hundreds, not sure why).
Bytes ingress and egress appear to always be zero.

@peterbourgon
Copy link
Contributor

"TCP connections" indeed represents the number of TCP connections that are attached to the thing you've clicked on. More specifically, it's the maximum number of observed TCP connections for every core node that composes the rendered node. Can you think of a better way to express that? "Active TCP connections"?

Bytes ingress and egress are indeed always zero (for now) and will be hidden in an upcoming point release.

@squaremo
Copy link
Author

squaremo commented Jun 2, 2015

"TCP connections" indeed represents the number of TCP connections that are attached to the thing you've clicked on.

Hmm, well I guess the numbers were surprising then, so perhaps the lesson is that being able to find out what those connections represent would be useful.

Bytes ingress and egress are indeed always zero (for now)

Oh OK. I can imagine those being quite useful -- "not done yet" is an understandable answer though.

@squaremo squaremo closed this as completed Jun 2, 2015
@peterbourgon
Copy link
Contributor

Filed #158 for that enhancement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants