Skip to content
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

Support log rotation customization in fluent.conf #3363

Closed
kenhys opened this issue May 7, 2021 · 0 comments · Fixed by #3352
Closed

Support log rotation customization in fluent.conf #3363

kenhys opened this issue May 7, 2021 · 0 comments · Fixed by #3352
Labels
feature request *Deprecated Label* Use enhancement label in general

Comments

@kenhys
Copy link
Contributor

kenhys commented May 7, 2021

Is your feature request related to a problem? Please describe.

In the current version, log rotation options were supported as
--log-rotate-age or --log-rotate-size via command line options.

On Windows, if you use td-agent package, fluentd is launched as a
windows service, it is required to configure again via
--reg-winsvc-fluentdopt or edit fluentdopt registry key for
customization.

This approach is not convenient for Windows (especially td-agent)
users, so it may be better to support more comprehensive solution -
customize via configuration file.

Describe the solution you'd like

Add configuration parameter to customize by log section.

<system>
  <log>
    rotate_age 5
    rotate_size 1048576
  </log>
</system>

Describe alternatives you've considered

N/A

Additional context

If this approach is implemented, we need to update https://docs.fluentd.org/deployment/system-config

working on #3352

@kenhys kenhys added the feature request *Deprecated Label* Use enhancement label in general label May 7, 2021
@kenhys kenhys linked a pull request May 7, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request *Deprecated Label* Use enhancement label in general
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant