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
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Use Cases
When using the file sink, log files will grow indefinitely. We need to manage rotation with an external tool (like logrotate). It'd be conveniant to be able to handle rotation in vector (time based, size based, number of old logs to keep, compression)
Attempted Solutions
No response
Proposal
No response
References
No response
Version
No response
The text was updated successfully, but these errors were encountered:
Hi @dani ! Thanks for opening this. We'd previously discussed similar functionality in #2057 and came to the conclusion that Vector should just defer to, and work well with, external tools like logrotate rather than building in log rotation capabilities to Vector itself. Given that, I'll close this issue out, but let me know if there are use-cases you can think of that Vector could handle that something logrotate couldn't or if you have other reasons you think Vector should have this functionality.
OK thanks. I tried to avoid logrotate (as it's often a pain to use. In my case, I can't even rely on it because of it's strange and hardcoded permission checks on log dir). Anyway, I worked around it with a naive copy + truncate + compress script based on size.
A note for the community
Use Cases
When using the file sink, log files will grow indefinitely. We need to manage rotation with an external tool (like logrotate). It'd be conveniant to be able to handle rotation in vector (time based, size based, number of old logs to keep, compression)
Attempted Solutions
No response
Proposal
No response
References
No response
Version
No response
The text was updated successfully, but these errors were encountered: