anchor.diff:  
   There are several different kinds of conditions but they all have one thing in common, each requires some piece of data against which the condition is evaluated.  Here are the different kinds of conditions:
   
  -* Threshold
  -** X < 10, X >= 20
  -* ThresholdRange
  -** X inside [10,20), X outside [100,200]
  +* Availability
  +** X is DOWN
   * Compare
   ** X < 80% Y
  -* String
  -** X starts with "ABC", X matches "A.*B"
  -* Rate
  -** X > 10 per-minute
  -* Availability
  -** X is DOWN
   * Event
   ** event.id starts 'IDXYZ', event.tag.category == 'Server',
      event.tag.from ends '.com'
   * Missing
   ** No event/data received for X in the last 5 minutes
  +* Nelson
  +** Detect Rule1,Rule2 scenarios for X
  +** https://en.wikipedia.org/wiki/Nelson_rules
  +* Rate
  +** X > 10 per-minute
  +* String
  +** X starts with "ABC", X matches "A.*B"
  +* Threshold
  +** X < 10, X >= 20
  +* ThresholdRange
  +** X inside [10,20), X outside [100,200]
   
   Most conditions deal with numeric data.  But String and Availability data is also supported.  A trigger can combine conditions dealing with data of different types and from different sources.
   
  
positive.code: 
  Tags on triggers are automatically passed on to the Alerts or Events generated by that trigger.  This allows the same search criteria used to fetch triggers to also be used to fetch the alerts or events generated by those triggers.
  
  A tag's name and value must both be non-empty.  But tag search allows for matching just the name by specifying value='*' in the search criteria.
  
  
  == REST API
  
  Hawkular Alerting supports a robust REST API for managing Triggers, Alerts and Events.  For more on how to generate API documentation, see the README.adoc at http://github.com/hawkular/hawkular-alerts[Hawkular-Alerts @ *GitHub*].
  
  
  == External Alert Integration
  
  
negative.code: * Aerogear integration
  * File-system notification
  * Webhook notification
  * Elasticsearch integration
  
  
  === Trigger Dampening
  