I would like to add attributes, specifically client request and response headers, to the OpenTelemetry span for each REST call. For the OpenTelemetry Java agent instrumentation, I would take advantage of the configuration parameters

otel.instrumentation.http.client.capture-request-headers
otel.instrumentation.http.client.capture-response-headers

but the Quarkus instrumentation does not provide an implementation of these.

Per @brunobat and the Q&A discussion #44256, it would be possible to add support for these config parameters:

Th implementation should be straight forward. We need to create the new properties to control the feature and add attributes to the span in this class:

quarkus/extensions/opentelemetry/runtime/src/main/java/io/quarkus/opentelemetry/runtime/tracing/intrumentation/restclient/OpenTelemetryClientFilter.java

Line 44 in 6ccff48

public class OpenTelemetryClientFilter implements ClientRequestFilter, ClientResponseFilter {

and this one as well:

quarkus/extensions/opentelemetry/runtime/src/main/java/io/quarkus/opentelemetry/runtime/tracing/intrumentation/resteasy/OpenTelemetryClassicServerFilter.java

Line 21 in e559cbd

public class OpenTelemetryClassicServerFilter implements ContainerRequestFilter {