This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 3e63f5bf852 chore(doc): camel-mdc notes (#19386)
3e63f5bf852 is described below
commit 3e63f5bf85213a5a0c8a0eb47ca66497040cae19
Author: Pasquale Congiusti <[email protected]>
AuthorDate: Wed Oct 1 13:28:23 2025 +0200
chore(doc): camel-mdc notes (#19386)
---
docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_15.adoc | 4 ++++
docs/user-manual/modules/ROOT/pages/mdc.adoc | 2 ++
2 files changed, 6 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_15.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_15.adoc
index 019e9508495..7f80c78b6d5 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_15.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_15.adoc
@@ -101,3 +101,7 @@ For more information, the related issue is CAMEL-22334.
|===
org.apache.camel.component.langchain4j.web.search.LangChain4jWebSearchEngine.Headers
was empty and has been removed
+
+=== camel-mdc
+
+We have introduced a new component, `camel-mdc`, whose goal is to simplify the
usage of logging MDC (Mapped Diagnostic Context) by allowing the user to
configure the Exchange headers and properties to use to trace in MDC logging
format.
diff --git a/docs/user-manual/modules/ROOT/pages/mdc.adoc
b/docs/user-manual/modules/ROOT/pages/mdc.adoc
index ff98814edeb..86c0e840056 100644
--- a/docs/user-manual/modules/ROOT/pages/mdc.adoc
+++ b/docs/user-manual/modules/ROOT/pages/mdc.adoc
@@ -2,6 +2,8 @@
The Mapped Diagnostic Context is a technology used in Java to provide a set of
customized information into each log trace. The major logging frameworks
implements it, and, although it may have certain limitations, this technology
is used to enhance the logging and monitoring of a Java application (Camel
applications included).
+NOTE: you're invited to try the new
ref:components::mdc-component.adoc[camel-mdc] component for an improved user
experience.
+
The main limitation of this technology is the fact that it stores values on a
context that is available at thread level. Since Camel is an application that
manages multiple thread, when it deals with asynchronous calls, the context
propagation may not work correctly.
NOTE: the framework should generally handle MDC correctly. However, there
could be components (eg, tracing components) and other asynchronous parts of
the system that still require the implementation of the context propagation:
please report if you notice anything wrong.
