anchor.diff:  
   At startup, every Packetbeat agent registers itself to the network topology by
   publishing to Elasticsearch the IP and port together with its agent name. This
  -information is used to set both the ``server`` and ``client_server`` fields
  +information is used to set both the `server` and `client_server` fields
   from transactions even when they are sniffed by another agent.
   
  -==== Tags
  +Example:
  +
  +[source,yaml]
  +------------------------------------------------------------------------------
  +agent:
  +  name: "my-agent"
  +------------------------------------------------------------------------------
  +
  +===== tags
   
   The tags of the agent are included in the `tags` field with each transaction
   published. Tags make it easy to group servers by different logical properties.
  
positive.code:       in promiscuous mode.
  
  
  ==== Snaplen
  
  The *snaplen* option controls the maximum size of the packets to capture. You
  generally want to set this to the MTU size used in your network. If the
  capturing *device* is "any" or "lo", the default value of this parameter is
  16436. Otherwise, it is 1514.
  
  [source,yaml]
  
negative.code: each of them the tag "webservers" and then use filters and queries in the
  Kibana web interface to get visualisations for the whole group of servers.
  
  Example:
  
  [source,yaml]
  ------------------------------------------------------------------------------
  agent:
    tags: ["my-service", "hardware", "test"]
  ------------------------------------------------------------------------------
  
  ===== ignore_outgoing
  
  If the `ignore_outgoing` option is enabled, Packetbeat agent ignores all the
  transactions initiated from the server running the agent.
  