OpenTelemetry capture request/response body?

[edeandrea]

Is there a way in an OpenTelemetry trace to capture the request/response body of an HTTP call? It seems that other things are already being captured on both the client & server side of a call. Is there a way I could capture the json of the response?

[quarkus-bot[bot]]

/cc @brunobat (opentelemetry), @radcortez (opentelemetry)

[radcortez]

Not currently. The request and response bodies are not part of the semantic conventions for capturing HTTP information: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md.

We discussed some time ago, about allowing the user to provide extractors to customize the trace information. Right now, the only way is to manually inject the Span and add the new attributes directly.

[edeandrea]

Can you point me to where those filters are in the otel stuff so I can take a look?

[brunobat]

Hi @edeandrea. The Classic rest client instrumentation wiring can be found here: https://github.com/quarkusio/quarkus/blob/main/extensions/opentelemetry/runtime/src/main/java/io/quarkus/opentelemetry/runtime/tracing/intrumentation/restclient/OpenTelemetryClientFilter.java#L64
If you move a package up you will find the other instrumentations.

[brunobat]

BTW, I don't think it is a good practice to store requests and responses from prod environments for several reasons, being the main one PII.

[edeandrea]

BTW, I don't think it is a good practice to store requests and responses from prod environments for several reasons, being the main one PII.

Completely agree. My use case is for a demo where I was to visualize the requests and responses through a bunch of services as part of an overall user interaction.

Rather than build something myself to do that I thought piggy-backing on tools that already exist (Otel/Jaeger/etc) might be my fastest/easiest approach.

[brunobat]

Sure. That should work fine