anchor.diff:  
   `actions`:: (list of action configs, optional) An ordered list of actions to execute when event is fired.
   
  -`waitFor`:: (string, optional) The time to wait between generating new events, as an integer number immediately followed by unit symbol, one of `s` (seconds), `m` (minutes), or `h` (hours). Default is `0s`.
  +`waitFor`:: (string, optional) The time to wait between generating new events, as an integer number immediately
  +followed by unit symbol, one of `s` (seconds), `m` (minutes), or `h` (hours). Default is `0s`. A condition must
  +persist at least for the `waitFor` period to generate an event.
   
   `enabled`:: (boolean, optional) When `true` the trigger is enabled. Default is `true`.
   
  
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: those that are explicitly excluded by `node` config property won't be reported at all.
  
  
  This trigger supports the following configuration:
  
  `collections`:: (string, optional) comma-separated list of collection names to monitor, or any collection if empty / not set.
  
  