anchor.diff:    other target branch in the main project).
   * When writing a commit message please follow http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html[these conventions],
     if you are fixing an existing issue please add `Fixes gh-XXXX` at the end of the commit
  -  message (where XXXX is the issue number).
  +  message (where XXXX is the issue number).
positive.code: ----
  
  ==== Importing into Intellij
  Spring Cloud needs a specific version of maven and a profile
  enabled. Intellij 14.1+ requires some configuration to ensure these are setup properly.
  
   1. Click New, Project from Existing Sources, choose your spring-cloud-sleuth directory
   2. Choose Maven, and select Environment Settings. *Ensure you are using Maven 3.3.3*
   3. In the next screen, *Select the profile `spring`* click Next until Finish.
   4. Click Build, Rebuild Project, and you are ready to go!
  
  ==== Importing into other IDEs
  Maven is well supported by most Java IDEs. Refer to you vendor documentation.
  
  == Contributing
  
  
negative.code: * If `spring-cloud-sleuth-stream` then the app will generate and collect traces via Spring Cloud Stream. Your app automatically becomes a producer of tracer messages that are sent over your broker of choice (e.g. RabbitMQ, Apache Kafka, Redis).
  
  If using Zipkin or Stream, configure the percentage of spans exported using `spring.sleuth.sampler.percentage` (default 0.1, i.e. 10%).
  
  NOTE: the SLF4J MDC is always set and logback users will immediately see the trace and span ids in logs per the example above. Other logging systems have to configure their own formatter to get the same result. The default is `logging.pattern.level` set to `%clr(%5p) %clr([${spring.application.name:},%X{X-Trace-Id:-},%X{X-Span-Id:-},%X{X-Span-Export:-}]){yellow}` (this is a Spring Boot feature for logback users).
  
  == Running the samples
  
  