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

change default file_completed_action behavior in read mode #223

Open
inqueue opened this issue Nov 29, 2018 · 2 comments
Open

change default file_completed_action behavior in read mode #223

inqueue opened this issue Nov 29, 2018 · 2 comments

Comments

@inqueue
Copy link

inqueue commented Nov 29, 2018

When in read mode, file_completed_action defaults to delete which means data can be lost. Can we please consider changing this default behavior? Requiring explicit configuration to delete processed files is much more preferable.

  • Version: 6.5.1
  • Config File:
input {
  file {
    path => [ "/var/log/some-log.json" ]
    codec => "json"
    mode => "read"
    sincedb_path => "/dev/null"
    file_completed_log_path => "/Users/jbryan/stack/support-help-issues/issues.log"
  }
}
@danhermann
Copy link

I am also encountering users who are surprised and/or confused that their input files are being deleted, often because they are unaware of the default setting for file_completed_action.

@gypark
Copy link

gypark commented Apr 10, 2020

Hello, Is there any new information about this?

I totally agree with @inqueue. I was very surprised just minutes ago, when I realized I had come to delete my original data

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants