dstat showing incorrect tcp active sockt count?

[siddharth178]

dstat showing incorrect tcp active sockt count?

[dagwieers]

I see what you mean now. Dstat did not show any unit numbers, and only reserved 3 columns in total for most connection stats. Should be fixed now !

[siddharth178]

Btw, noticed one thing. Proc file /proc/net/tcp used by dstat doesn't have this information. That means there is no issue in dstat code. But the real issue is with data available in /proc/net/tcp.

I checked if other tools have this issue -
Tested same scenario with 'ss' and it shows correct number of active/connected sockets.

Whats missing here? Is /proc/net/tcp right choice to look for this data?

[kkalinin]

I've noticed the same problem. And changing tab width for dstat_socket class helps. It's value hardcoded as 3 and it shows only first 3 digits of actual number. So everything is correct while you have <= 999 sockets in any state, but if you have 1234 socket in some state, dstat will show only 1.

[scottchiefbaker]

Is the solution just to display those numbers in decimal format? 1.2k connections?

[kkalinin]

I thought that the best solution would be to add one more app launch argument, something like --raw.
So, by default, the view would be human-readable. In case with tcp sockets - 1.2k, 1.2m, but in raw mode I would like to see the actual numbers, no matter of their length. But, for sure, some metrics like sent/recv bytes etc. should remain human-readable in any mode.
Still, as a quick solution, your idea is good!

Thank you!

[dagwieers]

@kkalinin You get the raw numbers in CSV output. We cannot print raw numbers to the screen since it messes up the whole formatting to the point it is rendered useless. (That's the problem with e.g. vmstat)

Currently one can already add --float to get floating point numbers instead of integers (when units are used). But we have to consider column width.

[dagwieers]

BTW Option --raw already exists, but doesn't do what you'd be expecting :-)

[superheizai]

Want to know how did you resolve this problem?
I suffer from the same problem. I want to measure system performance with one command,dstat, but it gave me a totally different number from ss.

[dagwieers]

@superheizai It is fixed in the master branch. The fix is included in commit 4c47a34