anchor.diff:  
   This may be a convenient option if error handling logic is the same regardless of which handler produced the error.
   
  -Also, error messages sent to the `errorChannel` can be published to a specific destination at the broker by configuring a binding named `error` for the outbound target.
  +Also, error messages sent to the `errorChannel` can be published to the specific destination at the broker by configuring a binding named `error` for the outbound target.
   This option provides a mechanism to automatically send error messages to another application bound to that destination or for later retrieval (for example, audit).
   For example, to publish error messages to a broker destination named `myErrors`, set the following property:
   
  
positive.code: ----
  spring.cloud.stream.bindings.error.destination=myErrors.
  ----
  
  ===== System Error Handling
  
  
negative.code: spring.cloud.stream.rabbit.bindings.input.consumer.republish-to-dlq=true
  ----
  
  Doing so forces the internal error handler to intercept the error message and add additional information to it before publishing it to DLQ.
  Once configured, you can see that the error message contains more information relevant to the original error, as follows:
  
  [source,text]
  