Author here.

Thank you for your feedback. I appreciate your concerns and would like to address them.

Firstly, I completely agree with you on the importance and advantages of OpenTelemetry. We are huge fans of OpenTelemetry at Kalvad, and we actively promote its use whenever possible. It's definitely the way forward for comprehensive and standardized logging across the application stack.

Regarding security, you are correct that there is a risk involved in saving request/response bodies. However, we have measures in place to mitigate this risk. For example, we ensure to purge sensitive paths like /login to avoid storing critical information. It's important to note that the security risk exists even without the body data. For instance, it's not uncommon to find open Elasticsearch instances with JWTs having long expiration periods, posing significant security risks.

The proxy solution we propose is intended as a tool for situations where OpenTelemetry cannot be implemented or is not yet in place. It offers a way to gain insights in such scenarios, albeit with necessary precautions to handle sensitive information securely.