Suggested indirectly via @kocolosk in his presentation at http://www.erlang-factory.com/upload/presentations/552/kocoloski-erlang-writ-large.pdf slides 13-15.
These stats are per TCP port. Mapping the port to the remote Erlang node name would be tremendously useful, then exposing each group of TCP stats in a JSON object keyed by the remote node name?
OTP docs: http://www.snookles.com/erlang-docs/R15B01/lib/kernel-2.15.1/doc/html/inet.html#getstat-2
@jmshoffs0812 @angrycub Time for some belated repo curating ... looking for CSE input.
Well, I am a firm believer that more stats are better than less. Even if this wasn't directly available in the typical stats pipeline, but was callable more like riak-admin top, it looks like useful information.
marking for 2.1