anchor.diff:  storing of metrics, alerting on incoming events and more. Those projects are developed
   in their own GitHub repositories and integrated in this project.
   
  -== About Alerts
  +link:http://www.slideshare.net/ponceballesteros/hawkular-alerting[Hawkular Alerting Introduction].
  +
  +== Project layout
   
   The project is divided into several modules
   
  
positive.code:     cd hawkular-alerts
      mvn clean install
  ```
  
  == Integration tests
  
  
negative.code: | hawkular-alerts-rest |
  This is a public REST API for alerts component. +
  It is a wrapper of the main *hawkular-alerts-api*.
  | hawkular-alerts-actions |
  Common API for action plugins. +
  An action plugin will be deployed as a .war artifact.
  | hawkular-alerts-actions-plugins |
  Alert actions plugins. +
  Main responsabilities are: +
  - Publish supported properties. +
  - Process actions messages.
  | hawkular-alerts-filter-api |
  Filter API to query which dataIds are published from triggers defined. +
  This info helps to filter and send only the relevant data needed for triggers evaluation.
  | hawkular-alerts-bus |
  This component is responsible for the communication between the alerts engine and the bus. +
  *hawkular-alerts-engine* is decoupled from the bus, so it can be used in other scenarios +
  (i.e. standalone, third party alerts system).
  | hawkular-alerts-bus-api |
  This is the public API for message objects used in *hawkular-alerts-bus*.
  |=======================
  
  == Getting started
  