Broker message provenance tracking
MP-Corelight opened this issue · comments
As a user of a high-volume Zeek instance that sometimes gets overloaded, I would like to know where message are coming from, where they're being sent, and how many are being sent, so that I can isolate the source of load issues and address them.
I moved this over into the broker repo, since it makes more sense to track a feature like this over there.