-
-
Notifications
You must be signed in to change notification settings - Fork 360
Snoop
Mogens Heller Grabe edited this page Sep 26, 2013
·
17 revisions
Snoop is a badly named simple MSMQ queue inspector, does some stuff that can't easily be done otherwise:
- provides a way to inspect your MSMQ queues
- can decode Rebus messages
- can copy/move/delete messages
- can show exception details of failed messages
- can move failed messages back to the source queue (i.e. "retry messages")
- can purge and delete queues
- can show the contents of the transactional dead-letter queue
You can download a ZIP file with Snoop here: http://mookid.dk/oncode/wp-content/2013/09/Rebus.Snoop_.zip
Basic stuff
- Home
- Introduction
- Getting started
- Different bus modes
- How does rebus compare to other .net service buses?
- 3rd party extensions
- Rebus versions
Configuration
Scenarios
Areas
- Logging
- Routing
- Serialization
- Pub sub messaging
- Process managers
- Message context
- Data bus
- Correlation ids
- Container adapters
- Automatic retries and error handling
- Message dispatch
- Thread safety and instance policies
- Timeouts
- Timeout manager
- Transactions
- Delivery guarantees
- Idempotence
- Unit of work
- Workers and parallelism
- Wire level format of messages
- Handler pipeline
- Polymorphic message dispatch
- Persistence ignorance
- Saga parallelism
- Transport message forwarding
- Testing
- Outbox
- Startup/shutdown
Transports (not a full list)
Customization
- Extensibility
- Auto flowing user context extensibility example
- Back off strategy
- Message compression and encryption
- Fail fast on certain exception types
Pipelines
- Log message pipelines
- Incoming messages pipeline
- Incoming step context
- Outgoing messages pipeline
- Outgoing step context
Prominent application services