Make ServiceInsight and Pulse understand the NServiceBus.Bridge.Transfer header

[andreasohlund]

The header syntax is explained here https://docs.particular.net/nservicebus/bridge/configuration#auditing

[mauroservienti]

@andreasohlund can you please explain what should be the SI and SP behavior?

[dvdstelt]

Currently the Bridge adds a header that shows from where to where the Bridge is shoveling the message. So azure service bus -> msmq could be a header. We think it should probably be visible when you

• retry messages, although this is needs some thought. do users want to know if the message came from another transport, because we don't modify any header when bridging error messages? We know we're on a specific transport, does the header help showing something useful?
• show message flow in ServiceInsight, so that it's clear messages bridged a transport
• etc