memory
by default (buf_memory) for the ease of testing, however file
(buf_file) buffer type is always recommended for the production deployments. If you use file
buffer type, buffer_path
parameter is required.max_retry_wait
is reached.retry_limit
parameter for details), the sleep interval can be up to approximately 131072 seconds (roughly 36 hours) in the default configurations.retry_limit
is ignored and there is no limit). The default values are 17 and false (not disabled). If the limit is reached, buffered data is discarded and the retry interval is reset to its initial value (retry_wait
).20.0
seconds. Note that parameter type is float
, not time
.<secondary>
with any output plugin in <match>
configuration. If the retry count exceeds the buffer's retry_limit
(and the retry limit has not been disabled via disable_retry_limit
), then buffered chunk is output to <secondary>
output plugin.<secondary>
is useful for backup when destination servers are unavailable, e.g. forward, mongo and other plugins. We strongly recommend out_file
plugin for <secondary>
.%Y%m%d%H
, which creates one file per hour.file
by default (buf_file). The memory
(buf_memory) buffer type can be chosen as well. If you use file
buffer type, buffer_path
parameter is required.max_retry_wait
is reached.retry_limit
parameter for details), the sleep interval can be up to approximately 131072 seconds (roughly 36 hours) in the default configurations.retry_limit
is ignored and there is no limit). The default values are 17 and false (not disabled). If the limit is reached, buffered data is discarded and the retry interval is reset to its initial value (retry_wait
).40.0
seconds.