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: == Logging
  
  Spring Cloud Data Flow is built upon several Spring projects, but ultimately the dataflow-server is a 
  Spring Boot app, so the logging techniques that applies to any link:http://docs.spring.io/spring-boot/docs/current/reference/html/howto-logging.html#howto-logging[Spring Boot] 
  application is applicable here as well. 
  
  
  While troubleshooting, following are the two primary areas where enabling the DEBUG logs could be 
  
negative.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 are being passed
  around source, processor and sink channels, you'd be deploying the stream with the following
  options.
  
  
  