davsclaus commented on code in PR #23534:
URL: https://github.com/apache/camel/pull/23534#discussion_r3304733251
##########
components/camel-micrometer-observability/src/main/docs/micrometer-observability.adoc:
##########
@@ -173,3 +171,30 @@ public void process(Exchange exchange) throws Exception {
mySpan.end();
}
----
+
+=== Baggage customization
+
+`Baggage` is a way to attach key-value metadata to a request and carry it
across service boundaries. In the context of telemetry technologies, baggage
travels along with the context (like trace/span), but it's meant for custom
data you define, not telemetry internals. Camel allows you to programmatically
provide any `Baggage` information via header settings. Whenever the component
finds an header defined as `MICROMETER_BAGGAGE_xyz` it will consider it as a
baggage variable named `xyz`. For example, in Java DSL:
+
+[source,java]
+----
+ from("direct:start")
+ .setHeader("MICROMETER_BAGGAGE_myValue",
constant("1234"))
Review Comment:
Hmm wont this cause baggage leaks over protocols as headers are part of the
user data. Should this not be exchange properties instead. Those are not sent
over the wire. Also a good idiom is to use CamelXXX style as reserved for Camel
functionality
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
