From 9dbdbb6ca11c84ac69feb12fb821698460f058ca Mon Sep 17 00:00:00 2001
From: Marcin Grzejszczak <marcin.grzejszczak@gmail.com>
Date: Wed, 1 Apr 2020 08:54:23 +0200
Subject: [PATCH] Updated docs

---
 docs/src/main/asciidoc/features.adoc | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/docs/src/main/asciidoc/features.adoc b/docs/src/main/asciidoc/features.adoc
index 7fa30f13c..9b2f84b36 100644
--- a/docs/src/main/asciidoc/features.adoc
+++ b/docs/src/main/asciidoc/features.adoc
@@ -56,6 +56,9 @@ NOTE: The SLF4J MDC is always set and logback users immediately see the trace an
 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.
+
+IMPORTANT: 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`).