On Mar 16, 2016, at 4:03 AM, Heiko W.Rupp <hrupp@redhat.com> wrote:

Hey Stefan,

On 15 Mar 2016, at 21:00, Stefan Negrea wrote:

 * Add support for metrics baselines; automatically computed
server-side and stored

How? What is the algorithm behind? Please remember that the
algorithm from RHQ is/was flawed.

The algorithm was indeed flawed, but I think the feature could be a big one. For those not familiar, in RHQ we used averages. http://apmblog.dynatrace.com/2012/11/14/why-averages-suck-and-percentiles-are-great/ is a nice article that explains why using averages is not good. I think that adding support for a histogram metric type that is calculated on the server gets a lot of what we need.


7) ElasticSearch integration
 * An optional integration with Elastic Search for tasks beyond the
capability of Cassandra.
 * Basic examples for this are whole tenant searches and aggregation
of text based data, such as tags, events, and even availability.

How do we deal with the data nodes of ES? Where do
the events of  "aggregation of events" come from and
are stored?
What does "whole tenant searches" mean?

--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschäftsführer: Paul Argiry, Charles Cachera, Michael Cunningham,
Michael O'Neill
_______________________________________________
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev