opentelemetry-specification

opentelemetry-specification copied to clipboard

What are you trying to achieve?

I want to capture request and response bodies. The content can be used for business transaction monitoring and security.

To move this forward we need:

• data semantics e.g. http.request.body/http.response.body or be transport agnostic e.g. request.body, response.body.
• a configuration for auto instrumentations e.g. OTEL_INSTRUMENTATION_CAPTURE_REQUEST_BODY=bool

Additional context.

• business transaction monitoring http://trasier.com/
• capture request and response bodies in Java https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/1317

Related https://github.com/open-telemetry/opentelemetry-specification/issues/1061#issuecomment-704409768

EDIT: But here it may make sense to keep in one issue to define if we even want to support this at all. It seems problematic, both from a performance and also privacy perspective.

EDIT: But here it may make sense to keep in one issue to define if we even want to support this at all. It seems problematic, both from a performance and also privacy perspective.

This is an opt-in feature not enabled by default only users who need this would enable it with all the implications of course.

This would be very useful for certain scenarios

Hello please has there been any progress made here. This specification would be really helpful in many enterprise Environments for also in many app dev scenarios for distributed trace of app data flow validations

upvoted this request :-) would be really usefull

+1