anchor.diff:  ===== tls
   
   Configuration options for TLS parameters like the root CA for Logstash connections. See
  -<<configuration-output-tls>> for more information. If the `tls` section is missing, a TCP-only connection is assumed. Logstash must also be configured to use TCP for
  -Logstash input.
  +<<configuration-output-tls>> for more information. To use TLS, you must also configure the 
  +https://www.elastic.co/guide/en/logstash/current/plugins-inputs-beats.html[Beats input plugin for Logstash] to use SSL/TLS.
   
   ===== timeout
   
  
positive.code: ==== Redis Output (DEPRECATED)
  
  The Redis output inserts the events in a Redis list. This output plugin is compatible with
  the http://logstash.net/docs/1.4.2/inputs/redis[Redis input plugin] from Logstash,
  so the Redis Output for the Beats is deprecated.
  
  Example configuration:
  
negative.code: ==== Logstash Output
  
  The Logstash output sends the events directly to Logstash by using the lumberjack
  protocol, which runs over TCP. To use this option, you must
  {libbeat}/getting-started.html#logstash-setup[install and configure] the Beats input
  plugin for Logstash. Logstash allows for additional processing and routing of
  generated events.
  
  Every event sent to Logstash contains additional metadata for indexing and filtering:
  