anchor.diff:  [[changed-configuration-options]]
   ==== Changed configuration file options
   
  -With the refactoring of the configuration file, some options were also removed or renamed. Below is a list with the changed entries:
  +With the refactoring of the configuration file, some options were also removed or renamed.
  +Below is a list with the changed entries:
   
   [cols="2*", options="header"]
   |===
  
positive.code: from packages or `C:\ProgramData\filebeat\registry` if you run as a Windows
  service.
  
  For enhancements reasons, especially for Windows
  the structure of the registry file has been changed. This makes a migration
  complex and leads to potential errors.
  
  Instead of a migration of the registry file we recommend to start Filebeat on
  the same host and send the log files to a different index.  This will start
  indexing from scratch. In case it is preferred to start at the end of all
  files, the option `tail_on_rotate` option can be set to true.
  
  The above will allow to keep the old Logstash-Forwarder running and it can be
  slowly switched over to Filebeat.
  
  === Migrate your configuration
  
  Logstash-Forwarder uses JSON + comments for its configuration file while
  Filebeat uses YAML for consistency with the other Beats. Like the
  Logstash-Forwarder, Filebeat also accepts reading multiple configuration files
  from a `conf.d` directory with similar restrictions. So the conversion can be
  done in most cases 1 to 1 on a per file basis.
  
  We recommend to first read the <<filebeat-configuration-details>> section which
  documents the Filebeat options.
  
negative.code: ==== TLS is off by default
  
  If you follow the section on migrating the configuration you will have TLS
  enabled, but you must be aware that if the tls section is missing from the
  configuration Filebeat uses an unencrypted connection to talk to Logstash.
  
  ==== Logging
  