Lowering log level of "chunk bytes limit exceeds for an emitted event stream" logs to trace

[raytung]

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

[daipom]

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.

fluentd/lib/fluent/plugin/buffer.rb

Lines 678 to 684 in 0a6d706

	if format && empty_chunk
	if chunk.bytesize > @chunk_limit_size
	log.warn "chunk bytes limit exceeds for an emitted event stream: #{adding_bytesize}bytes"
	else
	log.warn "chunk size limit exceeds for an emitted event stream: #{chunk.size}records"
	end
	end