From 010ce1d26992290ec68bbe0f41dbf8007ce8cc84 Mon Sep 17 00:00:00 2001
From: buildmaster <buildmaster@springframework.org>
Date: Wed, 8 Feb 2017 09:43:35 +0000
Subject: [PATCH] Sync docs from master to gh-pages

---
 spring-cloud-sleuth.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spring-cloud-sleuth.html b/spring-cloud-sleuth.html
index c82c461fb..df2e1156e 100644
--- a/spring-cloud-sleuth.html
+++ b/spring-cloud-sleuth.html
@@ -1389,7 +1389,7 @@ If using Zipkin or Stream, configure the percentage of spans exported using <cod
 <td class="content">
 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
- <code>logging.pattern.level</code> set to <code>%clr(%5p) %clr([${spring.application.name:},%X{X-B3-TraceId:-},%X{X-B3-SpanId:-},%X{X-Span-Export:-}]){yellow}</code>
+ <code>logging.pattern.level</code> set to <code>%5p [${spring.zipkin.service.name:${spring.application.name:-}},%X{X-B3-TraceId:-},%X{X-B3-SpanId:-},%X{X-Span-Export:-}]</code>
  (this is a Spring Boot feature for logback users).
  <strong>This means that if you&#8217;re not using SLF4J this pattern WILL NOT be automatically applied</strong>.
 </td>