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
{{ message }}
This repository was archived by the owner on Mar 11, 2026. It is now read-only.
Is your feature request related to a problem? Please describe.
Today some requests might contain oversized log entries which cause entire write request to be dropped instead just of oversized log entries to be dropped (see log-limits for more information). Describe the solution you'd like
The solution for this problem is to add partialSuccess flag in configuration so it can be added to each request as described in request-body. Given a fact that this library is used by other libraries, it will also give an opportunity to set partialSuccess globally.
In addition, the partialSuccess default value will be set to true in configuration, so it will provide more reliable logs generation. Describe alternatives you've considered
Today we have a custom logic to truncate oversized log entries by setting maxEntrySize parameter. Unfortunately truncating JSON structured log entries is complex and building generic solution for reduction JSON data is hard to achieve, thus generic solution is out of scope.
Is your feature request related to a problem? Please describe.
Today some requests might contain oversized log entries which cause entire write request to be dropped instead just of oversized log entries to be dropped (see log-limits for more information).
Describe the solution you'd like
The solution for this problem is to add
partialSuccessflag in configuration so it can be added to each request as described in request-body. Given a fact that this library is used by other libraries, it will also give an opportunity to setpartialSuccessglobally.In addition, the
partialSuccessdefault value will be set totruein configuration, so it will provide more reliable logs generation.Describe alternatives you've considered
Today we have a custom logic to truncate oversized log entries by setting
maxEntrySizeparameter. Unfortunately truncating JSON structured log entries is complex and building generic solution for reduction JSON data is hard to achieve, thus generic solution is out of scope.