-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Td-agent.log file size keep on increasing #3538
Comments
Moved to fluent/fluent-package-builder#342 |
Hello @ashie I tested with the below configuration, it's not working, 1048 means 1kb right ?? After happens if that limit is reached, my file size is more than 2Mb and it's still growing.
I was confused where to the above settings so I have tried in 2 locations: C:\opt\td-agent\lib\ruby\gems\2.7.0\bundler\gems\fluentd-b6e76c09d60e\Fluent.conf Below is my configuration. Fluentd version: 4.1.1 |
TD Agent 4.1.1 bundles fluentd 1.12.3, |
@kenhys So, it should work on the version that I'm using, could you please let me where this should be updated ?? C:\opt\td-agent\lib\ruby\gems\2.7.0\bundler\gems\fluentd-b6e76c09d60e\Fluent.conf And what should be the behaviour after the configuration is done??? |
No, It will not work because you use Fluentd v1.12.3 (maybe).
If you using Fluentd v1.13.0 or later, |
Oh, It should be followed on fluent/fluent-package-builder#342 |
Describe the bug
The log file (C:\opt\td-agent\td-agent.log) is increasing continuously, how to put a limit ??
There is some configuration like file rotate and there is a command however we have a fluentd running as windows service, so if there is any configuration could you please suggest either in conf file or while running the fluentd service from powershell.
To Reproduce
Keep fluentd service running and process different messages the file size keeps increasing.
Expected behavior
The old contents in the file should be deleted after a certain limit is reached.
Your Environment
Your Configuration
Your Error Log
No Errors it's physical size issue.
Additional context
No response
The text was updated successfully, but these errors were encountered: