anchor.diff:  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. For Filebeat the additional
  -config files must be in a different directory then the main config file. The 
  +config files must be in a different directory then the main config file. 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
  
positive.code:       - localhost:5043
  
      tls: <2>
        # The path to your client ssl certificate
        certificate: ./logstash-forwarder.crt
        # The path to your client ssl key
        certificate-ssl: ./logstash-forwarder.key
  
        # The path to your trusted ssl CA file. This is used
        # to authenticate your downstream server.
        certificate-authorities:
          - ./logstash-forwarder.crt
  
        # Network timeout in seconds.
  
negative.code: -------------------------------------------------------------------------------------
  
  <1> When multiple hosts are defined, the default behavior in Filebeat is to
      pick a random host for new connections, similar to the Logstash-Forwarder
      behavior. Filebeat can optionally do load balancing, see
      {libbeat}/configuration.html#loadbalance[the configuration option].
  <2> Note that if the `tls` section is missing then TLS is disabled. It is
      automatically enabled when adding the `tls` section. More TLS options are
      documented {libbeat}/configuration.html#configuration-output-tls[here].
  
  
  [[changed-configuration-options]]
  