Since Rebus'incoming messages pipeline andoutgoing 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)).(...)

whereverbose: true means that each pipeline step's detailed documentation will be included in the output, andverbose: false will restrict the output to show just the type names of the steps.