[Hawkular-commits] [hawkular/hawkular-alerts] 420d3f: WIP: Data filtering

[Jay Shaughnessy]

  Branch: refs/heads/winter/filtermetrics
  Home:   https://github.com/hawkular/hawkular-alerts
  Commit: 420d3f5a00af96337c32acdd5aa280ed1ec018ad
      https://github.com/hawkular/hawkular-alerts/commit/420d3f5a00af96337c32acdd5aa280ed1ec018ad
  Author: Jay Shaughnessy <jshaughn at redhat.com>
  Date:   2015-03-27 (Fri, 27 Mar 2015)

  Changed paths:
    A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/services/DefinitionsEvent.java
    A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/services/DefinitionsListener.java
    M hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/services/DefinitionsService.java
    A hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/init/CacheManager.java
    M hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/listener/AvailDataListener.java
    M hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/listener/MetricDataListener.java
    M hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/impl/DbDefinitionsServiceImpl.java
    M hawkular-alerts-rest/src/main/java/org/hawkular/alerts/rest/TriggersHandler.java

  Log Message:
  -----------
  WIP: Data filtering
Another pass, this time currently removing the use of infinispan and just
using a listener approach.  Also, consolidates the filter handling into
a Singleton. And added avail data id filtering.

This all works fine where everything is co-located. What we may want to
do is keep it like this but also have the "cachemanager" drop info in the
cache in order to notify other servers of updates.

Also, currently the event info is very coarse, we could make things more
granular and/or provide more contextual data, perhaps even the affected
ids, and therefore avoid total refreshes of the active id lists.