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
I've installed per the instructions for v4 here and as indicated the service was created.
I failed initially to set the log level appropriately for the system logs, so they were filling up the folder on my VM. That's on me, and I've since adjusted it. The fact that the excessive logs filled the drive struck me as odd so I looked for log rotation options.
But when I visit the system config page and the fluentd logging page I can't find instructions on how I could configure the windows service to rotate logs. Information about how to do this via command-line is provided, but the install guide and the automatic installation of the service suggest I should be able to use the agent via a service but if logs can't be set to rotate then I'm always at some risk of filling the drive.
Given the service is set up, I prefer to take advantage of it if I can, rather than trying to find another way of setting up the agent to start after machine restarts etc. But if it's just going to eventually fill the drive I'm not sure I have a choice.
Thanks in advance for any help.
The text was updated successfully, but these errors were encountered:
I've installed per the instructions for v4 here and as indicated the service was created.
I failed initially to set the log level appropriately for the system logs, so they were filling up the folder on my VM. That's on me, and I've since adjusted it. The fact that the excessive logs filled the drive struck me as odd so I looked for log rotation options.
But when I visit the system config page and the fluentd logging page I can't find instructions on how I could configure the windows service to rotate logs. Information about how to do this via command-line is provided, but the install guide and the automatic installation of the service suggest I should be able to use the agent via a service but if logs can't be set to rotate then I'm always at some risk of filling the drive.
Given the service is set up, I prefer to take advantage of it if I can, rather than trying to find another way of setting up the agent to start after machine restarts etc. But if it's just going to eventually fill the drive I'm not sure I have a choice.
Thanks in advance for any help.
The text was updated successfully, but these errors were encountered: