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
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.
The text was updated successfully, but these errors were encountered:
Follow-up discussions in Ingest channel (Wed, March 28). Broader discussions are underway on best approach/messaging. Hold off iomplementing this one for now.
We should better communicate two things with the file input docs:
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.
The text was updated successfully, but these errors were encountered: