Handlers

jobstat: keyed by handler — the same execution counts, sliced by the code that ran rather than the type that was published.

For an ordinary IJob the two tabs agree: one type, one handler. For a routed IMessage they do not. One message fans out to every subscribed handler, so a single row on Job types becomes several rows here, one per subscriber that consumed it.

That difference is the point of the tab. When a message type looks slow, this is where you find out which subscriber is slow instead of blaming the publish.