Inject transport messageId into headers for debug and investigation

Riaan · June 5, 2019, 1:30pm

At my company we’ve experienced some hiccups using Service Bus, we opened a support ticket and got some assistance from Particular, we also opened support tickets with Microsoft to little effect as they were not able to track down the messages on their side, due to us not being able to provide the MessageId

My question: Is it possible to get access to the MessageId assigned by the transport, in this case, Azure Service Bus, and assign it to the headers for potential debugging scenarios?

SeanFeldman · June 7, 2019, 4:32pm

Hi Riaan,

Unfortunately, this is currently not possible. I’ve raised a feature request on your behalf.
Please subscribe to it to get notified and add comments to provide more details.

github.com/Particular/NServiceBus

Preserving native (transport) message ID

opened 04:31PM - 07 Jun 19 UTC

closed 12:09PM - 01 Oct 19 UTC

SeanFeldman

Improvement

## Context When an NServiceBus endpoint sends a message, the message sent mig…ht have two message IDs: 1. A native message ID (from the underlying transport infrastructure) 1. And NServiceBus message ID expressed by [`NServiceBus.MessageId`](https://docs.particular.net/nservicebus/messaging/headers#messaging-interaction-headers-nservicebus-messageid) header. ## Issue When there's a need to investigate what happened to processed or failed messages, there are audit and error messages. Unfortunately, those messages contain NServiceBus message ID **only** and have no reference to the native message ID of the processed messages, which are often required by the infrastructure provider to identify what happened to the original message. Access to the native message ID is not possible in Core as the message ID is replaced with `NServiceBus.MessageId` headers' value upon the physical message injection prior to the `IIncomingPhysicalMessageContext` invocation. This context, while exposing `IncomingMessage`, has no longer access to the native message ID as it's [lost during `IncomingMessage` construction](https://github.com/Particular/NServiceBus/blob/f44644bd6ed8144abe97141ee5e56ab2fb5ab3bb/src/NServiceBus.Core/Transports/IncomingMessage.cs#L23). ## Suggestion Allow access to the native message ID by adding it to the headers or expose another way to access that value. E.g. add a property to `IncomingMessage` to expose native message ID.

Thank you,
Sean