From 18d57f9508ceca8816e5da8ff8f225cba7623325 Mon Sep 17 00:00:00 2001 From: DeDe Morton Date: Fri, 29 Apr 2016 00:20:08 -0700 Subject: [PATCH] Add info about LSF to Beats input plugin option for Filebeat migration (#1524) --- filebeat/docs/migration.asciidoc | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/filebeat/docs/migration.asciidoc b/filebeat/docs/migration.asciidoc index d59d2221bad..a1637207496 100644 --- a/filebeat/docs/migration.asciidoc +++ b/filebeat/docs/migration.asciidoc @@ -34,6 +34,16 @@ Logstash Forwarder to Filebeat, we recommend that you keep the Lumberjack plugin Beats input plugin on the same Logstash instances, but set up the Beats input plugin to use a different port. After you have migrated all the machines to Filebeat, you can remove the Lumberjack plugin. +We realize that opening additional ports may not be feasible in your organization. Another option for phased migration +to Filebeat is to ship data from Logstash Forwarder directly to the Beats input plugin. + +IMPORTANT: This data shipping path is only supported for migrating to Filebeat and will no longer be supported when Logstash Forwarder reaches https://www.elastic.co/support/eol[End of Life]. + +What's required? + +* The https://www.elastic.co/guide/en/logstash/current/plugins-inputs-beats.html[Beats input plugin for Logstash] +version 2.2.8 or later. +* SSL must be explicitly enabled in the Beats input plugin (`ssl => true`) because SSL is on by default with Logstash Forwarder. The SSL/TLS configs should be the same for both the Logstash Forwarder and Filebeat instances. == Updating the Registry File