anchor.diff:  
   ===== process
   
  -The `process` option for each process defines the name of the process, as it
  -appears in the published transactions. The name doesn't have to match the name
  -of the executable, feel free to choose something more descriptive (e.g. "my
  -app" instead of "gunicorn")
  +The name of the process as it will appear in the published transactions. The name 
  +doesn't have to match the name of the executable, so feel free to choose something 
  +more descriptive (for example,  "myapp" instead of "gunicorn").
   
   ===== cmdline_grep
   
  -This option for each process is used to identify the process at
  -runtime. When it starts, and then periodically, Packetbeat scans the process table for
  -processes matching `cmdline_grep` option. The match is done against the
  -process' command line as read from `/proc/<pid>/cmdline`.
  -
  -For each of these processes, it monitors which file descriptors it has opened.
  -When a new packet is captured, it reads the list of active TCP connections and
  -matches the corresponding one with the list of file descriptors.
  -
  +The name used to identify the process at run time. When Packetbeat starts, and then 
  +periodically afterwards, it scans the process table for
  +processes that match the values specified for this option. The match is done against the
  +process' command line as read from `/proc/<pid>/cmdline`.
positive.code: 
  ===== device
  
  Configures the network devices from which the traffic is
  captured. The configured device is set automatically in promiscuous mode,
  meaning that it can capture traffic from other hosts of the same LAN.
  
  [source,yaml]
  ------------------------------------------------------------------------------
  
negative.code: 
  ===== parseunknown
  
  When this option is enabled, it forces the memcache text protocol parser to accept unknown commands.
  
  NOTE: Unknown commands MUST NOT contain a data part.
  
  ===== maxvalues
  
  The maximum number of values to store in the message (multi-get).
  All values will be base64 encoded.
  
  The possible settings for this option are:
  
  * `maxvalue: -1`, which stores all values (text based protocol multi-get)
  * `maxvalue: 0`, which stores no values (default)
  * `maxvalue: N`, which stores up to N values
  
  ===== maxbytespervalue
  
  The maximum number of bytes to be copied for each value element.
  
  NOTE: Values will be base64 encoded, so the actual size in the JSON document will be 4 times the value that 
  you specify for `maxbytespervalue`.
  
  ===== udptransactiontimeout
  
  The transaction timeout in milliseconds. The defaults is 10000 milliseconds.
  
  NOTE: Quiet messages in UDP binary protocol get responses only if there is an error. 
  The memcache protocol analyzer will wait for the number of milliseconds specified by 
  `udptransactiontimeout` before publishing quiet messages. Non-quiet messages or 
  quiet requests with an error response are published immediately.
  
  
  ==== MySQL and PgSQL Configuration Options
  
  ===== max_rows
  
  The maximum number of rows from the SQL message to publish to Elasticsearch. The
  default is 10 rows.
  
  
  ===== max_row_length
  
  The maximum length in bytes of a row from the SQL message to publish to
  Elasticsearch. The default is 1024 bytes.
  
  [[configuration-thrift]]
  ==== Thrift Configuration Options
  
  The Thrift protocol has several specific configuration options. Here is a
  sample configuration section:
  
  [source,yaml]
  