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

Better document recommended usage of the file input #174

Open
acchen97 opened this issue Mar 28, 2018 · 2 comments
Open

Better document recommended usage of the file input #174

acchen97 opened this issue Mar 28, 2018 · 2 comments
Assignees

Comments

@acchen97
Copy link

We should better communicate two things with the file input docs:

  • Filebeat should be the recommended solution for log extraction.
  • When absolutely required, the file input should only be used for file tailing.

Perhaps a banner statement similar to this would go a long way:

"For all log file extraction use cases, Filebeat is the strongly recommended solution coupled with Logstash or Elasticsearch for further processing and analytics. When required, the file input plugin for Logstash should only be used for the file tailing use case."

/cc @jsvd @tsg would appreciate your feedback as well.

@karenzone
Copy link
Contributor

Follow-up discussions in Ingest channel (Wed, March 28). Broader discussions are underway on best approach/messaging. Hold off iomplementing this one for now.

@fbaligand
Copy link

@acchen97
With the new PR that is currently reviewed (#171 ), file input will have an option to indicate "tail" or "read" mode.

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

3 participants