-
-
Notifications
You must be signed in to change notification settings - Fork 364
Log message pipelines
Since Rebus' incoming messages pipeline and outgoing messages pipeline are so crucial in determining Rebus' behavior, it can be useful to log their contents at startup.
This is especially the case if you change Rebus' behavior by configuring things that alter the pipelines. E.g. enabling message compression and/or encryption will inject steps in the right places, both for incoming and outgoing messages.
You can log the pipelines by doing this:
Configure.With(...)
.(...)
.Options(o => o.LogPipeline(verbose: true))
.(...)
where verbose: true
means that each pipeline step's detailed documentation will be included in the output, and verbose: false
will restrict the output to show just the type names of the steps.
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