<!-- Thanks for raising a Spring Boot issue. What sort of issue are you raising?

Currently not able to add request body/response body to HTTP tracing. The option is not there in Include.class.

Previously we could extend WebRequestTraceFilter and add any options...

How do we do this in Spring Boot 2?

Thanks in advance :)

Comment From: fat-panda

request body/response body or parameters are not part of the Included options in http trace in the Spring Boot 2 actuator.

we were able to do this previously by extending WebRequestTraceFilter and adding any option..

How has the functionality changed? Is this no longer supported?

Thanks in advance

Comment From: wilkinsona

HTTP tracing in 2.0 is intentionally less flexible than it was in 1.5. The flexibility of the implementation in 1.5 caused a number of problems and made it impossible to support on top of WebFlux, Spring MVC, and Jersey. Tracing the request and response body has never been supported out of the box. Support for tracing parameters was dropped as, when the request is POSTed form data, it requires reading the entire request body. If you want to capture one or both of these, and I would recommend that you don't, you should implement your own endpoint.

Comment From: ahmedju

Please any update for this requirement ?

Comment From: wilkinsona

@ahmedju This remains something that we do not want to support. Please see my comment above and the discussion on https://github.com/spring-projects/spring-boot/issues/23907 for further details.

Comment From: ahmedju

@ahmedju This remains something that we do not want to support. Please see my comment above and the discussion on #23907 for further details.

Thanks for reply. Excuse me is there any way, any way, to add new endpoint to view request/response for Actuator? custom Bean?

Comment From: wilkinsona

23907 and the gist to which it links contains one possible approach. The best way to do it really depends on the web stack(s) that you want to support and how you want to store the request and response bodies for subsequent retrieval.

If you have any further questions, please follow up on Stack Overflow or Gitter. As mentioned in the guidelines for contributing, we prefer to use GitHub issues only for bugs and enhancements.