anchor.diff:  
   ===== backoff
   
  -Backoff values define how aggressively Filebeat crawls new files for updates
  -The default values can be used in most cases. Backoff defines how long it is waited
  -to check a file again after EOF is reached. Default is 1s which means the file
  -is checked every second if new lines were added. This leads to a near real time crawling.
  -Every time a new line appears, backoff is reset to the initial value.
  -Default: 1s
  +The backoff options specify how aggressively Filebeat crawls new files for updates.
  +You can use the default values in most cases.
  +
  +The `backoff` option defines how long Filebeat
  +waits before checking a file again after EOF is reached. The default is 1s, which means
  +the file is checked every second if new lines were added. This enables near real-time crawling. Every time a new line appears in the file, the `backoff` value is reset to the initial
  +value. The default is 1s.
   
   ===== max_backoff
   
  -Max backoff defines what the maximum waiting time is. After having backed off multiple times
  -from checking the files, the waiting time will never exceed max_backoff independent of the
  -backoff factor. Having it set to 10s means in the worst case a new line can be added to a log
  -file after having backed off multiple times, it takes a maximum of 10s to read the new line.
  -Default: 10s
  +The maximum time for Filebeat to wait before checking a file again after EOF is
  +reached. After having backed off multiple times from checking the file, the wait time
  +will never exceed `max_backoff` regardless of what is specified for  `backoff_factor`.
  +Because it takes a maximum of 10s to read a new line, specifying 10s for `max_backoff` means that, at the worst, a new line could be added to the log file if Filebeat has
  +backed off multiple times. The default is 10s.
   
   ===== backoff_factor
   
  -The backoff factor defines how fast the waiting time is increased. The bigger the backoff factor,
  -the faster the max_backoff value is reached. The backoff increments exponential.
  -The minimal value allowed is 1. If this value is set to 1 it means backoff algorithm is disabled
  -and the backoff value is used for waiting for new lines.
  -The backoff value will be multiplied each time with the backoff_factor until max_backoff is reached.
  -Default: 2
  +This option specifies how fast the waiting time is increased. The bigger the
  +backoff factor, the faster the `max_backoff` value is reached. The backoff factor
  +increments exponentially. The minimum value allowed is 1. If this value is set to 1,
  +the backoff algorithm is disabled, and the `backoff` value is used for waiting for new
  +lines. The `backoff` value will be multiplied each time with the `backoff_factor` until
  +`max_backoff` is reached. The default is 2.
   
   ===== partial_line_waiting
   
  -Defines the time on how long the harvester will wait for a line to be completed.
  -Sometimes a lines it not completely written when checked by Filebeat. Filebeat
  -will wait for the time defined below so the system can complete the line.
  -In case the line is not completed in this time, the line will be skipped.
  -Default: 5s
  +Sometimes Filebeat checks a line before it's completely written. This option specifies
  +how long the harvester waits for the system to complete a line before skipping that line. The default is 5s.
   
   ===== force_close_files
   
  -This option closes a file, as soon as the file name changes.
  -This config option is recommended on windows only. Filebeat keeps the files it's reading open. This can cause
  -issues when the file is removed, as the file will not be fully removed until also Filebeat closes
  -the reading. Filebeat closes the file handler after ignore_older. During this time no new file with the
  -same name can be created. Turning this feature on the other hand can lead to loss of data
  -on rotate files. It can happen that after file rotation the beginning of the new
  -file is skipped, as the reading starts at the end. We recommend to leave this option on false
  -but lower the ignore_older value to release files faster.
  -Default: false
  +By default, Filebeat keeps the files that it’s reading open until the timespan specified by `ignore_older` has elapsed. This behaviour can cause issues when a file is removed. Because the file isn't fully removed until Filebeat closes the file, no new file with the same name can be created during this time.
  +
  +You can force Filebeat to close the file as soon as the file name changes by setting the `force_close_windows_files` option to true. This option is supported on Windows only. The default is false.
  +
  +Turning on this option can lead to loss of data on rotated files. After file rotation, the beginning of the new file might be skipped because the reading starts at the end of the file. We recommend that you leave this option set to false, and instead specify a lower value for the `ignore_older` option to release files faster.
   
   ===== spool_size
   
  -Event count spool threshold - forces network flush if exceeded.
  -
  +The event count spool threshold. This setting forces a network flush if the specified
  +value is exceeded.
  +
  +[source,yaml]
   -------------------------------------------------------------------------------------
   filebeat:
     spool_size: 1024
  
positive.code: [[filebeat-configuration-details]]
  == Configuration Options
  
  The configuration file of Filebeat uses http://yaml.org/[YAML] as any other Beat.
  To start with the configuration it is best to have a look at the default configuration. It is described in detail
  what each configuration option is for and how it can be used. Remove the items that are not needed for your setup.
  
  The _etc/filebeat.yml_ consists of the following sections:
  
  * {libbeat}/configuration.html#configuration-shipper[Shipper]
  * {libbeat}/configuration.html#configuration-output[Output]
  
negative.code: 
  ===== encoding
  
  The file encoding to use for reading files that contain international characters.
  See the encoding names http://www.w3.org/TR/encoding/[recommended by the W3C for use in HTML5].
  
  Here are some sample encodings from W3C recommendation:
  
      * plain, latin1, utf-8, utf-16be-bom, utf-16be, utf-16le, big5, gb18030, gbk, hz-gb-2312,
      * euc-kr, euc-jp, iso-2022-jp, shift-jis, and so on
  
  The `plain` encoding is special, because it does not validate or transform any input.
  