This is an automated email from the ASF dual-hosted git repository.

pcongiusti 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 46b21dfc69b8 chore(docs): proper indentation
46b21dfc69b8 is described below

commit 46b21dfc69b8e98e41a9977a5fa04e4210f62dde
Author: Pasquale Congiusti <[email protected]>
AuthorDate: Fri Apr 10 10:13:09 2026 +0200

    chore(docs): proper indentation
    
    Ref CAMEL-23283
---
 .../src/main/docs/micrometer-observability.adoc                       | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git 
a/components/camel-micrometer-observability/src/main/docs/micrometer-observability.adoc
 
b/components/camel-micrometer-observability/src/main/docs/micrometer-observability.adoc
index e502d493ee54..ed333f6ff7be 100644
--- 
a/components/camel-micrometer-observability/src/main/docs/micrometer-observability.adoc
+++ 
b/components/camel-micrometer-observability/src/main/docs/micrometer-observability.adoc
@@ -127,7 +127,7 @@ NOTE: this is an example that can be used as a reference. 
It may not work exactl
 
 You can see that the configuration of this component may get a bit difficult, 
unless you are already familiar with the tracing technology you're going to 
implement.
 
-=== How to trace
+== How to trace
 
 Once the application is instrumented and configured, you can observe the 
traces produced with the tooling compatible to the concrete implementation you 
have in place. You are invited to follow the specific documentation of each 
technology.
 
@@ -135,7 +135,7 @@ Once the application is instrumented and configured, you 
can observe the traces
 
 Your application may require a Java agent in order to get the traces generated 
by the Camel application and push to the tracing server (ie, Opentelemetry 
based instrumentation). You may need to configure such agent (or any other 
tool) directly via Java parameters.
 
-=== MDC logging
+== MDC logging
 
 You can leverage the `traceHeadersInclusion` to include the generated 
`CAMEL_TRACE_ID` and `CAMEL_SPAN_ID` into the Camel Exchange and together with 
`camel-mdc` you can make those headers available in the MDC context (via 
`camel.mdc.customHeaders=CAMEL_TRACE_ID,CAMEL_SPAN_ID` configuration). This is 
the idiomatic way in Camel.
 

Reply via email to