This is a fundamental part of our day-to-day work life, we need to be constantly looking at API responses in our O11 development and production environments. We would love to have this feature in ODC as well.

Really it is great idea having access to full trace logs including request/response payloads would make it easier to troubleshoot complex API issues. Actually many teams migrating from OS11 are used to this feature. Bringing it to ODC ensures a smoother transition and a familiar debugging experience.Using  trace data developers can identify problems more efficiently saving time and effort. Trace logs often help with debugging production issues and tracking data for compliance purposes. But one concern is tracing should come with clear privacy controls to ensure no sensitive or PII data is logged insecurely. 

This is great idea

As a developer, having the ability to trace APIs along with their request and response payloads is extremely helpful during debugging. Introducing this capability in ODC would greatly benefit developers by enabling quicker identification of errors, ultimately contributing to faster and more efficient development within the platform. 

Good suggestion. Having request and response details in ODC traces will really help with debugging and make things easier for developers.

As said by the people above me, this is CRUCIAL in daily supporting applications.

If OutSystems ever wondered why partners and customers complain about not having feature parity between O11 and ODC, this is one of the reasons. 

How ridiculous is it to have to add an onRequest and onResponse on every API to log this crucial information, especially since this logging has been available in O11 and many versions before that.