[Hawkular-dev] Properties store?

[Lukas Krejci]

In my mind almost anything "is changing like a metric", because everything
changes over time.

Also IMHO  "key-value pairs" are just JSON. I think that the structured data
support for configs and operation params served us well in RHQ.

So IMHO we need a time-series store for structured data. I am not sure inventory
is that -  it is good for storing relationships among entities but I am not
sure if it is well suited for storing (versioned) structured data.

The reason for that is that such support would require somehow translating the
JSON-like format of the structured data into a graph of nodes in the underlying
graph database to enable any visibility of the constituent parts of the data
structure.

Alternatively, with Titan, it might be possible to achieve the same result
if we employed ElasticSearch as additional backend for it and configured it
to analyze the JSON. I have not yet looked into the possibilities, pros nor
cons of that approach.

Or just use ElasticSearch as a "properties store" straight away - both
inventory and IMHO metrics could benefit from having ES as part of the Hawkular
cluster for their own purposes but IMHO a dedicated properties store should
be geared towards storing, analyzing and querying structured data - which is 
the exact sales pitch of ES ;)

Now I'm not saying that I know anything more about ES than I just said - maybe
it's completely different and I'm blabbering nonsense here, but I guess the 
point I wanted to make is that inventory is not designed to store, query
or analyze structured data in and of itself.

Lukas

----- Original Message -----
> From: "Heiko W.Rupp" <hrupp at redhat.com>
> To: "Discussions around Hawkular development" <hawkular-dev at lists.jboss.org>
> Sent: Monday, 4 May, 2015 9:00:00 AM
> Subject: [Hawkular-dev] Properties store?
> 
> Hey,
> 
> in RHQ we had several ways to record properties of things
> * traits
> * resource configuration
> * plugin configuration
> * ...
> 
> I think we need something similar in Hawkular.
> 
> Having said that, we probably should avoid the above situation
> and find out what is really needed.
> 
> I can imagine that for stuff that are in reality changing attributes of
> a resource (e.g. version, #of cpus, ip address, ....) - basically stuff
> that is not changing like a metric, some key-value pairs on the
> resource in inventory may be the best place.
> 
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>