anchor.diff:  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.
  +is evaluating data to detect a problem while it will be a in *AUTORESOLVE* mode when it is evaluating data to detect that
  +the problem is longer present.
   
   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.
  
positive.code: 
  == AutoResolve triggers
  
  A trigger definition has one or multiple conditions that are set to detect a problem. When incoming data matches the
  condition expresions an alert is triggered to inform about this new issue. In this context, if the engine is still
  receiving data, new alerts will be generated even if it refers to the *same* problem.
  
  The detection of multiple alerts belonging to the *same* problem can be controlled with fine granularity.
  
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:
  
  