Clojurians Log v2

Found an alternative: https://opentelemetry.io/docs/languages/java/automatic/configuration/#capturing-http-request-and-response-headers

clj-otel has no influence on the agent. Please see the longer answer https://github.com/steffan-westcott/clj-otel/issues/17#issuecomment-2040695513.

Thanks, @steffan! Just for my own understanding of OTel semantics: clj-otel cannot add attributes to an existing span? They can only be set at the time the span is created?

The clj-otel function add-span-data! can be used to add attributes to an existing span. However, it is not advisable to add HTTP header attributes to a span created by the agent. The values of some HTTP headers may be security sensitive. When using the agent, one would expect the definitive list of headers to add to server spans to be specified in the agent configuration. It would be surprising if other headers not in that list were also added. In general, clj-otel can configured to add basic telemetry data for applications that are run without the agent, such as HTTP server spans and metrics. However, clj-otel is documented and designed not to add this data for applications that are run with the agent. The agent will always provide data of superior quality than data from clj-otel, because the agent is tightly integrated with the supported libraries.

Thanks for this additional context!

OpenTelemetry instrumentation agent 2.x has several https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v2.0.0, notably around some default OTLP protocols and semantic conventions. I suggest using migrating to 2.x as soon as is convenient. The clj-otel documentation and examples have been updated such that they assume agent 2.x is used.