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
Is your feature request related to a problem? Please describe.
Hey team 馃憢
From what I have gathered, fluentd did not split chunks if the event stream exceeds the chunk bytes limit, but this was changed in b5f2e9f.
Since we are now splitting chunks and retrying the chunks, I think this log (chunk bytes limit exceeds for an emitted event stream) is now more informational (and for debugging really) more than indicative of a potential issue.
Describe the solution you'd like
What are your thoughts on lowering this log line from warn to something like trace?
Describe alternatives you've considered
Leaving it - but it does generate a lot of logs
Additional context
No response
The text was updated successfully, but these errors were encountered:
I don't immediately get the meaning of the condition format && empty_chunk for this warning message.
I guess it is important what this condition is for.
Is your feature request related to a problem? Please describe.
Hey team 馃憢
From what I have gathered, fluentd did not split chunks if the event stream exceeds the chunk bytes limit, but this was changed in b5f2e9f.
Since we are now splitting chunks and retrying the chunks, I think this log (
chunk bytes limit exceeds for an emitted event stream
) is now more informational (and for debugging really) more than indicative of a potential issue.Describe the solution you'd like
What are your thoughts on lowering this log line from
warn
to something liketrace
?Describe alternatives you've considered
Leaving it - but it does generate a lot of logs
Additional context
No response
The text was updated successfully, but these errors were encountered: