Additional diagnostic properties on dispatch failure

[nimbusapi]

Additional diagnostic properties on dispatch failure

[uglybugger]

This would be really useful and a fairly simple intro to the project for anyone interested.

[michaelnoonan]

I've added timestamp, executing identity and machine name (in 43c30b9) but the failed path will be a bit more tricksy.

Should we take the "To" field as gospel, or the IMessageReceiver._path as gospel (and promote it to a property)?

[uglybugger]

Hmm.. I'm thinking the "To" field unless we can think of a good reason not to. Do you see this affecting what happens when we consolidate dead letters into a single queue?

[michaelnoonan]

I think it's a good idea. I copied To and ReplyTo into those Diagnostics
Headers when centralising dead letters, but ran into some situations where
To and ReplyTo were null, but didn't get to the bottom of why.

For centralising dead letters I used a Property called "FailedPath" or
similar so the infrastructure knows where to send the message for Replay.

On Sat, Feb 22, 2014 at 11:09 AM, uglybugger [email protected]:

Hmm.. I'm thinking the "To" field unless we can think of a good reason not
to. Do you see this affecting what happens when we consolidate dead letters
into a single queue?

Reply to this email directly or view it on GitHubhttps://github.com/DamianMac/Nimbus/issues/45#issuecomment-35789807
.