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

Add connection count to base OS checks. #379

Closed
drohr opened this issue Feb 21, 2013 · 8 comments
Closed

Add connection count to base OS checks. #379

drohr opened this issue Feb 21, 2013 · 8 comments
Assignees
Milestone

Comments

@drohr
Copy link

drohr commented Feb 21, 2013

Would be nice if dd-agent also got the amount of connections and added it to its "base" of stats to check, like disk space and memory today. Either something from netstat or fetch the data from proc. Maybe group on type, TCP/UDP and such.

$ cat /proc/net/sockstat
sockets: used 786
TCP: inuse 702 orphan 0 tw 4346 alloc 703 mem 382
UDP: inuse 22 mem 2
UDPLITE: inuse 0
RAW: inuse 0
FRAG: inuse 0 memory 0
@ghost ghost assigned LotharSee Feb 22, 2013
@LotharSee
Copy link
Contributor

Hi @drohr,
We are thinking about it and there is a lot of way to do that.
Does specific information (TCP/UDP, connection state, ...) really interest you?

@drohr
Copy link
Author

drohr commented Feb 28, 2013

On TCP/UDP, I think most users don't really care about UDP stuff, as its, UDP. So either look for just TCP connections or group on connection type.

On the connection type, I would guess you would like to create an alert based on if you have a large number of TIMED_WAIT. But this could of course be triggered inside your application instead. Information about current ESTABLISHED connections is always useful.

Other information that could be useful is group by port number.

Example what it could look like, but this really depends on what features you want to add, and how stuff is implemented. But I would love to hear some of your ideas.

diagram1

@drohr
Copy link
Author

drohr commented Feb 28, 2013

system.net.connections_tcp
system.net.connections_udp

and then being able to split it by connection state

@LotharSee
Copy link
Contributor

New networks metrics were added to the last release.
By default, we have 4 new metrics : system.net.packet_(in|out).(count|error). Interfaces defined in excluded_interface in conf.d/network.yaml won't return these metrics.

You can also enable tracking of TCP/UDP connections. In conf.d/network.yaml, set collect_connection_state: true. It will report a connection count by IPv4/IPv6, TCP/UDP and TCP state. Right now, it only works on Linux.

@mfractal
Copy link

mfractal commented Oct 9, 2015

any chance to add this functionality in windows @LotharSee ?

@vladimir-i
Copy link

Note that this issue requests the number of TCP connections but it was closed after the number of packets sent/received was added. Could the number of connections be added, please?

@jpza
Copy link

jpza commented Sep 26, 2017

Bump

@slmingol
Copy link

slmingol commented Dec 9, 2017

This should be reopened, it doesn't address the original ask. The ask was for individual tallys for specific ports, not just the aggregations of all ports in the given states.

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

6 participants