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
Describe the bug
Since I would like to set the index name as the format fluentd.${tag}.%Y%m, I need to set up the timekey for the buffer. However, after setting up the timekey, the flush_interval stops to work. It takes much longer to dump the data to the elastic search. If I remove the timekey setup, the log records can be dumped to elastic search immediately, while the index_name isn't correct.
Set flush_mode interval in <buffer>.
You see following message in fluentd logs.
'flush_interval' is ignored because default 'flush_mode' is not 'interval': 'lazy'
Thanks for your response. I removed the timekey attribute from the buffer section and change the flush_mode into immediate. In this case, even though the index was created immediately when I start the fluentd, the new records were not inserted into index immediately when there're new records appended to the log file. Do you know the possible reason for that?
Describe the bug
Since I would like to set the index name as the format
fluentd.${tag}.%Y%m
, I need to set up the timekey for the buffer. However, after setting up the timekey, the flush_interval stops to work. It takes much longer to dump the data to the elastic search. If I remove the timekey setup, the log records can be dumped to elastic search immediately, while the index_name isn't correct.To Reproduce
Fluentd config file:
Log file example:
Expected behavior
The log records should be dumped into elastic search quickly, rather than takes around 1 min.
Your Environment
The text was updated successfully, but these errors were encountered: