per-peer stats

[pgte]

We need these stats per peer because of ipfs-inactive/dynamic-data-and-capabilities#3 and ipfs/js-ipfs#1198.

[hacdias]

For ipfs/js-ipfs#1198, I'll need per-peer and per-protocol stats, of, at least total bandwidth in and total bandwidth out.

[pgte]

@hacdias can you define what you mean by "protocol"? Is it the bitswap protocol (1.0.0 or 1.1.0), the transport being used or the multiplexed protocol (DHT, bitswap, etc)?

(If it's the latest, we can't do this at the bitswap level).

[hacdias]

@pgte protocol is the transport being used. Just opened an issue on libp2p: libp2p/js-libp2p#157

[daviddias]

done with #166 , thanks @pgte :)

@hacdias anything else?

[hacdias]

@diasdavid what I really need to implement the Bandwidth Stats on js-ipfs is libp2p/js-libp2p#157 because it should measure all of the in and out bandwidth and not only bitswap.

[bvand]

@hacdias I'm new to ipfs, looking to help out on an issue like this to get started.

I was looking at ipfs/js-ipfs#1198 - just to confirm my understanding, Bandwidth stats are the only additional per-peer stats left to implement?
What is the current status? Is this something that it would make sense for me to jump on?

[bvand]

Found ipfs/js-ipfs#1230 - looks like this is complete then? Or is there more?

[hacdias]

Oh yes, this one is already done. Thanks @bvand