anchor.diff:  ----
   
   (_where, `org.springframework.integration` is the global package for everything Spring Integration related, 
  -which is responsible for messaging channels_)+which is responsible for messaging channels_)
  +
  +These properties can also be specified via `deployment` properties when deploying the stream.
  +
  +[source,bash]
  +----
  +dataflow:>stream deploy foo --properties "app.*.logging.level.org.springframework.integration=DEBUG"
  +----
positive.code: The streaming applications in Spring Cloud Data Flow are Spring Boot applications and they can be 
  independently setup with logging configurations. 
  
  For instance, if you'd have to troubleshoot the `header` and `payload` specifics that's being passed 
  around between source, processor and sink channels, you'd be deploying the stream with the following
  options.
  
  
  
negative.code: (_where, `reactor.ipc.netty` is the global package for everything `reactor-netty` related_)
  
  NOTE: Similar to the `local-deployer` and `cloudfoundry-deployer` options as discussed above, there
  are equivalent settings available for Apache YARN, Apache Mesos and Kubernetes variants, too. Check out the
  respective link:https://github.com/spring-cloud?utf8=%E2%9C%93&query=deployer[SPI implementations] to 
  find out more details about the packages to configure for logging.
  
  