Contents

• Getting Started
•     Overview
•     Architectural Principles
•     Transactions

• Samples
•     Web App Integration
•     Web App - Asp.Net Mvc3 Integration
•     Encryption
•     Full Duplex - Request/Response
•     Generic Host - Logging
•     PubSub
•     Versioning
•     Message Mutators
•     Unobtrusive
•     Data Bus
•     Scale Out

• Day to Day
•     Dependency Injection
•     Support for child containers
•     Logging
•     Messages as Interfaces
•     Introducing IEvent and ICommand
•     Unobtrusive mode messages
•     Unit Testing
•     One way/Send only endpoints

• Hosting
•     In Your Process
•     NServiceBus Host
•         Profiles
•     32-bit (x86) Host Process

• Management and Monitoring
•     Auditing
•     Monitoring
•     Msmq Information

• Scaling Out
•     Performance Information
•     Multi-Site with the Gateway
•         More about the Gateway
•     Multi-Server with the Distributor
•     Unit of work in NServiceBus 3.0
•         Unit Of Work implementation for RavenDB

• Publish-Subscribe
•     Overview
•     API and Configuration

• Long-Running Processes
•     Sagas

• Customization
•     Customizing Configuration

Auditing with NServiceBus

The scalability inherent in parallel message-driven systems
makes them more difficult to debug than their sequential,
synchronous and centralized counterparts.

For these reasons, NServiceBus provides message auditing
built-in to every endpoint. All you need to do is tell
NServiceBus where you want to send those messages.

Configuring Auditing

In order to turn on auditing, all you have to do is to add the attribute "ForwardReceivedMessagesTo" to the UnicastBusConfig section of an endpoint's configuration file as shown below:

The above configuration will cause all messages arriving at the given endpoint to be forwarded to the queue called "AuditQueue" on the machine called "AdminMachine". You can specify any queue on any machine, though only one is supported. Of course, you can forward on from that machines as well.

What you choose to do with those messages is now up to you - you can save them in a database, do some custom logging, anything.

The important thing is that you now have a centralized record of everything that's happening in your system while maintaining all the benefits of keep things distributed.

Next Steps

Learn more about how logging works in NServiceBus.