anchor.diff:  ===== reconnect_interval
   
   The interval for reconnecting failed Redis connections. The default is 1 second.
  +
  +===== bulk_max_size
  +
  +The maximum number of events to buffer internally during publishing. The default is 2048. 
  +
  +Specifying a larger batch size may add some latency and buffering during publishing. However, for Redis output, this 
  +setting does not affect how events are published.
  +
  +Setting `bulk_max_size` to values less than or equal to 0 disables buffering in libbeat. 
   
   [[file-output]]
   ==== File Output
  
positive.code: ===== pretty
  
  If `pretty` is set to true, events written to stdout will be nicely formatted. The default is false.
  
  [[configuration-output-tls]]
  
  
negative.code: 
  The default is 3.
  
  ===== bulk_max_size
  
  The maximum number of events to bulk in a single Logstash request. The default is 2048.
  
  If the Beat sends single events, the events are collected into batches. If the Beat publishes
  a large batch of events (larger than the value specified by `bulk_max_size`), the batch is
  split.
  
  Specifying a larger batch size can improve performance by lowering the overhead of sending events. 
  However big batch sizes can also increase processing times, which might result in
  API errors, killed connections, timed-out publishing requests, and, ultimately, lower
  throughput.
  
  Setting `bulk_max_size` to values less than or equal to 0 disables buffering in libbeat. When buffering is disabled,
  Beats that publish single events (such as Packetbeat and Topbeat) send each event directly to
  Elasticsearch. Beats that publish data in batches (such as Filebeat) send events in batches based on the
  spooler size.
  
  [[redis-output]]
  ==== Redis Output (DEPRECATED)
  
  