I was trying to get the traffic analyzer working at one point, but as far as I recall, you guys use a custom jussi structure. Which meant that my jussi wasn't really capable of working with the traffic analyzer. I'll maybe look into it later on.

I think what Rishi meant (as well as some other people I've heard from) is mainly revolving around the networking of hive.blog -- unfortunately, it seems like OVH's network has been relatively on fire (pun intended) for the last couple of months, causing dropouts from time to time or in the best-case scenario, sudden latency spikes. (usually lasting about 10-ish seconds, but it's enough for it to error out).

Unfortunately, it's really hard to get a "usage metric" per se with jussi. The best possible ways I found so far were -- link usage (per second), bandwidth use (per month) and active connections to the node.

I may write a post on it soon.

For benchmarking, I think @fullnodeupdate overall is doing a great job. While it is sometimes vague and counts things that may mess up the stats (block latency, for example, which isn't always accurate) it's a nice overlook to most nodes.