we need some way for engine to expose detailed egress information per connection type.
In MHOUSE we currently assume the sink is the destination for all egress bytes, this is not the case, since middle operators could be to different connection types. We should expose a new way to expose egress (and potentially ingress) bytes per connection type. This should include adding the BYTE_TARGET_WEBAPI target.

We should bring up the approach to the greater team