I've done that using message tracing with my introspection package. That basically covers all use cases I have for inspecting live traffic through my flows.
It also integrates the debug panel, so I can do all my filtering using that panel.
When I started talking about message tracing here in the forum, that was the first comment: don't do this, it will kill the editor performance. Well it didn't but just in case it does, I did recently add rate limiting to it.
Even if there is a risk of performance degradation, a little clarity/insight can go a long way so the trade off is probably well worth it.
