Multiline Parser: Discrepancy over default flush timeout
Relatively minor issue, but I noticed that there seems to be conflicting default values mentioned for the flush_timeout multiline parser parameter.
Specifically:
-
As per the multiline parsing doc, the default is 5 seconds
flush_timeout: Timeout in milliseconds to flush a non-terminated multiline buffer. Default is set to 5 seconds.
-
As per the comments in the built-in Docker multiline parser code, the default is 0.5 seconds
In case a message is not complete just wait until 500 milliseconds (0.5 second) and flush the buffer.
-
As per the actual multiline parser code, the default is 4 seconds
#define FLB_ML_FLUSH_TIMEOUT 4000 /* Flush timeout default (milliseconds) */
@pranavmarla Thanks for noticing. We will try to solve this.
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.
This issue was closed because it has been stalled for 5 days with no activity.
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.
This issue was closed because it has been stalled for 5 days with no activity.