In a continuous traffic environment, ./ecapture-perf tls --eventaddr=xxx.txt may generate a large ecapture file xxx.txt, is it possible to consider using golang rolling file library, such as lumberjack/rotatelogs, to integrate with zerolog and support automatic slicing of eventaddr specified files (the file handler that receives the captured event)? Thks