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
Logs before or after the file is rotated are not tracked.
Rotate_Wait, Refresh_Interval is the default value, but this amount was expected to be sufficiently tracked.
But there are untraceable numbers in between.
why is fluent-bit like this? Is that the intended move?
In real business logic, larger files are rotated every 5 minutes, but we tested them like this to reproduce similar issues in simple situations.
To Reproduce
Steps to reproduce the problem:
Run fluent-bit with tail input plugin for '/logs/test' file
Exec below script for collect log.
it is overwrite the file every multiple of 10 to imitate lotate file. and other numbers are added to the file.
#!/bin/bash
for i in {1..50}
do
if (( $i % 10 == 0 ))
then
echo "Overwrite: $i" > /logs/test
else
echo "Append: $i" >> /logs/test
fi
done
Expected behavior
Fluent-bit must be able to log all numbers from 1 to 50.
Screenshots
However, if you look at the log before or after the file is rotated, there are numbers that are not logged.
Bug Report
Describe the bug
Logs before or after the file is rotated are not tracked.
Rotate_Wait, Refresh_Interval is the default value, but this amount was expected to be sufficiently tracked.
But there are untraceable numbers in between.
why is fluent-bit like this? Is that the intended move?
In real business logic, larger files are rotated every 5 minutes, but we tested them like this to reproduce similar issues in simple situations.
To Reproduce
it is overwrite the file every multiple of 10 to imitate lotate file. and other numbers are added to the file.
Expected behavior
Fluent-bit must be able to log all numbers from 1 to 50.
Screenshots
However, if you look at the log before or after the file is rotated, there are numbers that are not logged.
Why did you do this?
Your Environment
Additional context
The text was updated successfully, but these errors were encountered: