You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using the http-logger plugin on some routes to log response bodies to an external service (with include_resp_body set to true). We have noticed that response bodies larger than 512 KB are being truncated and this is a problem because we need to handle bodies of several MBs in size without data loss.
Looking into the documentation, we found this #11133
It would be useful for us to have a similar solution for the http-logger, since we cannot use the kafka-one. Is there any chance this could be implemented also for the http-logger? Alternatively, how to overcome this difficulty?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are using the http-logger plugin on some routes to log response bodies to an external service (with include_resp_body set to true). We have noticed that response bodies larger than 512 KB are being truncated and this is a problem because we need to handle bodies of several MBs in size without data loss.
Looking into the documentation, we found this #11133
It would be useful for us to have a similar solution for the http-logger, since we cannot use the kafka-one. Is there any chance this could be implemented also for the http-logger? Alternatively, how to overcome this difficulty?
Beta Was this translation helpful? Give feedback.
All reactions