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
When Filebeat uses TCP input, we can set the option max_message_size as maximum size in bytes of the message received over TCP. But, there is another option that limits the message size when Filebeat calls
scanner.Scan()
to collect data: MaxScanTokenSize, the meaning of this option is the maximum size used to buffer a message. Filebeat does not override MaxScanTokenSize with max_message_size, which causes an error when the value of max_message_size we set is greater than MaxScanTokenSize and the length of our message is greater than MaxScanTokenSize and less than max_message_size. (position: filebeat/inputsource/tcp) . beats version: 6.5.4, but 7.0 also has this problem.
The text was updated successfully, but these errors were encountered:
When Filebeat uses
TCP input
, we can set the optionmax_message_size
as maximum size in bytes of the message received over TCP. But, there is another option that limits the message size when Filebeat callsto collect data:
MaxScanTokenSize
, the meaning of this option is the maximum size used to buffer a message. Filebeat does not overrideMaxScanTokenSize
withmax_message_size
, which causes an error when the value ofmax_message_size
we set is greater thanMaxScanTokenSize
and the length of our message is greater thanMaxScanTokenSize
and less thanmax_message_size
. (position:filebeat/inputsource/tcp
) . beats version: 6.5.4, but 7.0 also has this problem.The text was updated successfully, but these errors were encountered: