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