diff --git a/reference/html/README.html b/reference/html/README.html
index df1dd1564..027bc1052 100644
--- a/reference/html/README.html
+++ b/reference/html/README.html
@@ -1218,13 +1218,26 @@ The SLF4J MDC is always set and logback users immediately see the trace and span
shown earlier.
Other logging systems have to configure their own formatter to get the same result.
The default is as follows:
-logging.pattern.level set to %5p [${spring.zipkin.service.name:${spring.application.name:-}},%X{X-B3-TraceId:-},%X{X-B3-SpanId:-},%X{X-Span-Export:-}]
+logging.pattern.level set to %5p [${spring.zipkin.service.name:${spring.application.name:-}},%X{traceId:-},%X{spanId:-},%X{spanExportable:-}]
(this is a Spring Boot feature for logback users).
If you do not use SLF4J, this pattern is NOT automatically applied.
+
+
+
+|
+
+ |
+
+Starting with version 3.0.0, the logging pattern has changed.
+We’ve converted the MDC entries from B3 to non B3 keys (e.g. X-B3-TraceId to traceId).
+ |
+
+
+
diff --git a/reference/html/features.html b/reference/html/features.html
index 005c4d2d3..2e53037e8 100644
--- a/reference/html/features.html
+++ b/reference/html/features.html
@@ -225,13 +225,26 @@ The SLF4J MDC is always set and logback users immediately see the trace and span
shown earlier.
Other logging systems have to configure their own formatter to get the same result.
The default is as follows:
-logging.pattern.level set to %5p [${spring.zipkin.service.name:${spring.application.name:-}},%X{X-B3-TraceId:-},%X{X-B3-SpanId:-},%X{X-Span-Export:-}]
+logging.pattern.level set to %5p [${spring.zipkin.service.name:${spring.application.name:-}},%X{traceId:-},%X{spanId:-},%X{spanExportable:-}]
(this is a Spring Boot feature for logback users).
If you do not use SLF4J, this pattern is NOT automatically applied.
+
+
+
+|
+
+ |
+
+Starting with version 3.0.0, the logging pattern has changed.
+We’ve converted the MDC entries from B3 to non B3 keys (e.g. X-B3-TraceId to traceId).
+ |
+
+
+
logging.pattern.level set to %5p [${spring.zipkin.service.name:${spring.application.name:-}},%X{X-B3-TraceId:-},%X{X-B3-SpanId:-},%X{X-Span-Export:-}]
+logging.pattern.level set to %5p [${spring.zipkin.service.name:${spring.application.name:-}},%X{traceId:-},%X{spanId:-},%X{spanExportable:-}]
(this is a Spring Boot feature for logback users).
If you do not use SLF4J, this pattern is NOT automatically applied.
+
+
+
+|
+
+ |
+
+Starting with version 3.0.0, the logging pattern has changed.
+We’ve converted the MDC entries from B3 to non B3 keys (e.g. X-B3-TraceId to traceId).
+ |
+
+
+
diff --git a/reference/html/spring-cloud-sleuth.html b/reference/html/spring-cloud-sleuth.html
index 1ebec55ae..da1367f7d 100644
--- a/reference/html/spring-cloud-sleuth.html
+++ b/reference/html/spring-cloud-sleuth.html
@@ -1209,13 +1209,26 @@ The SLF4J MDC is always set and logback users immediately see the trace and span
shown earlier.
Other logging systems have to configure their own formatter to get the same result.
The default is as follows:
-logging.pattern.level set to %5p [${spring.zipkin.service.name:${spring.application.name:-}},%X{X-B3-TraceId:-},%X{X-B3-SpanId:-},%X{X-Span-Export:-}]
+logging.pattern.level set to %5p [${spring.zipkin.service.name:${spring.application.name:-}},%X{traceId:-},%X{spanId:-},%X{spanExportable:-}]
(this is a Spring Boot feature for logback users).
If you do not use SLF4J, this pattern is NOT automatically applied.
+
+
+
+|
+
+ |
+
+Starting with version 3.0.0, the logging pattern has changed.
+We’ve converted the MDC entries from B3 to non B3 keys (e.g. X-B3-TraceId to traceId).
+ |
+
+
+