anchor.diff:      "xpack.monitoring.collection.enabled": true
     }
   }
  ----------------------------------- 
  +----------------------------------
   
   If {es} {security-features} are enabled, you must have `monitor` cluster privileges to 
   view the cluster settings and `manage` cluster privileges to change them.
  +// end::enable-collection[]
   
  -// end::enable-collection[]
   For more information, see <<monitoring-settings>> and <<cluster-update-settings>>.
   --
   
   . {metricbeat-ref}/metricbeat-installation-configuration.html[Install {metricbeat}] on each
   {es} node in the production cluster.
   
  -. Enable the {es} {xpack} module in {metricbeat} on each {es} node. +
  +. Enable the {es} {xpack} module in {metricbeat} on each {es} node.
   +
   --
  -// tag::enable-es-module[]
   For example, to enable the default configuration in the `modules.d` directory, 
   run the following command:
   
  
positive.code: 
  .. Add the `username` and `password` settings to the {es} module configuration
  file. 
  // end::remote-monitoring-user[]
  --
  
  . Optional: Disable the system module in {metricbeat}.
  +
  --
  // tag::disable-system-module[]
  By default, the {metricbeat-ref}/metricbeat-module-system.html[system module] is
  enabled. The information it collects, however, is not shown on the *Monitoring*
  page in {kib}. Unless you want to use that information for other purposes, run
  
negative.code: 
  . {metricbeat-ref}/metricbeat-starting.html[Start {metricbeat}] on each node. 
  
  . Disable the default collection of {es} monitoring metrics.
  +
  --
  Set `xpack.monitoring.elasticsearch.collection.enabled` to `false` on the 
  production cluster.
  
  