anchor.diff:  those that are explicitly excluded by `node` config property won't be reported at all.
   
   
  -This trigger support the following configuration:
  +This trigger supports the following configuration:
   
   `collections`:: (string, optional) comma-separated list of collection names to monitor, or any collection if empty / not set.
   
  
positive.code: * `metric`: generated when the configured metric crosses a configured lower or upper threshold value
  * `indexSize`: generated when a shard size (defined as index size in bytes or number of documents)
  exceeds upper or lower threshold values
  * `searchRate`: generated when the 1-minute average search rate exceeds configured upper threshold
  * `scheduled`: generated according to a scheduled time period such as every 24 hours etc
  
  Events are not necessarily generated immediately after the corresponding state change occurred - the
  
negative.code: `nodeAdded` event this will be the time when the node was added and not when the event was actually
  generated, which may significantly differ due to the rate limits set by `waitFor`.
  
  `properties`:: (map, optional) Any additional properties. Currently includes eg. `nodeNames` property that
  indicates the nodes that were lost or added.
  
  == Auto Add Replicas Trigger
  
  