-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Additional diagnostic properties on dispatch failure #45
Comments
This would be really useful and a fairly simple intro to the project for anyone interested. |
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)? |
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? |
I think it's a good idea. I copied To and ReplyTo into those Diagnostics For centralising dead letters I used a Property called "FailedPath" or On Sat, Feb 22, 2014 at 11:09 AM, uglybugger notifications@github.comwrote:
|
When a dispatch failure occurs the Exception Type, Message and StackTrace are recorded as message properties. Add timestamp, failed path, executing identity and machine name to help diagnose dispatch failures.
The text was updated successfully, but these errors were encountered: