MassTransit Commute - Consuming Fault Events

MassTransit has extensive exception handling options, including retry and redelivery, and also supports poison messages by moving them to an error queue as well as publishing a Fault event. In this episode, consuming fault events is covered, including how to handle typed and untyped faults, as well as disable fault event publishing.

MassTransit Commutes are short, single subject videos focused on a specific feature, typically in response to questions from developers using MassTransit.

MassTransit

Connect with me on Twitter:

Sponsor me on GitHub:

[nacmop]

Chris, do you mind showing how to get the message payload with AnyFaultConsumer? I'm trying to create some publishing service that would notify me of any faults via email and including message and exceptions in it would be of a great help.
Thanks.

[BesarKutleshi-zw]

Hi man, I have a question about fault consumer. If I have two services that consume same event e.x account.created, if first service fails to handle this event but second service has handled it correctly, the second service is also receiving the fault event from first service, what can I do?

[PeterParker-nhdi]

Great video as always Chris. Something I would like to see is handling the scenario where you have a queue with multiple consumers all hitting a third party api that's rate limited. Is there functionality in Masstransit that can handle this?

[orozcohoyos]

hi chris!, im wondering if you could show me if there is some video where you covered the «Routing key» behavior.


in the software i'm working, i'm trying to figure out how to publish and consume a message but based in his namespace and a value from a property (this property is an enum), if you could help me i will be so thankfull with you!