anchor.diff:  
   == Alert Lifecycle
   
  -Alert definitions (triggers) are used to detect problems. When a problem happens a new alert is generated by the engine
  +Triggers are defined to detect problems. When a problem happens a new alert is generated by the engine
   with the information about the data that matched the defined conditions. Also an Alert provides a simple lifecycle to
   indicate the status of the problem.
   
  
positive.code: A trigger defines conditions that are responsible to detect a problem. These conditions are called *FIRING* conditions
  in Hawkular Alerts. Optionally, a trigger can define conditions that are responsible to detect when the problem is
  gone. These new ones are called *AUTORESOLVE* conditions. So, in the engine a trigger will be in *FIRING* mode when it
  is evaluating data to detect a problem while it will be a in *AUTORESOLVE* mode when it found out that the problem
  is not present anymore.
  
  These combination of *FIRING* and *AUTORESOLVE* conditions ensures that only *one alert* is generated for a problem
  and when the problem is resolved the trigger automatically returns to firing mode.
  
negative.code: 
  <1> *autoResolve* flag set to *true* indicates that the trigger will activate *FIRING* and *AUTORESOLVE* modes. Flag set
  to *false* will run the trigger only in *FIRING* mode.
  <2> *autoResolveAlerts* flag set to *true* will automatically mark all unresolved alerts (for the trigger) as *resolved*
  when *AUTORESOLVE* trigger detect problem is gone. Flag set to *false* will not modify the alert lifecycle.
  
  And the next fragment will show how to declare *FIRING* and *AUTORESOLVE* conditions linked with the trigger:
  
  