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

Could fluentd provide an option delete_after_read #4527

Open
ryan-611 opened this issue Jun 11, 2024 · 1 comment
Open

Could fluentd provide an option delete_after_read #4527

ryan-611 opened this issue Jun 11, 2024 · 1 comment
Labels
enhancement Feature request or improve operations

Comments

@ryan-611
Copy link

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

version: fluent/fluentd-kubernetes-daemonset:v1.16.5-debian-elasticsearch8-1.0
When we use in_tail plugin to upload our file to elasticsearch, we need to delete files after uploading.
But I can not found this option such as delete_after_read in otel file-receiver.

Describe the solution you'd like

Provide an option such as delete_after_read.

Describe alternatives you've considered

No alternatives right now

Additional context

No response

@daipom daipom added feature request *Deprecated Label* Use enhancement label in general and removed waiting-for-triage labels Jun 13, 2024
@daipom
Copy link
Contributor

daipom commented Jun 13, 2024

In the case of in_tail, it is assumed to collect general log files.
They are usually managed by mechanisms external to Fluentd, such as logrotate.
So, I guess Fluentd's standard features and standard plugins do not have such functionality.

What kind of cases do you assume?

When we use in_tail plugin to upload our file to elasticsearch, we need to delete files after uploading.

Isn't there any external mechanism that controls the survival time of those files?

@kenhys kenhys added enhancement Feature request or improve operations and removed feature request *Deprecated Label* Use enhancement label in general labels Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature request or improve operations
Projects
None yet
Development

No branches or pull requests

3 participants