[Hawkular-dev] availability and metric endpoints

[Lukas Krejci]

+100, very well said.

I wasn't 100% sure if config was really the right candidate to be stored in 
metrics, I just saw the many similarities and potentials for reuse of the 
existing code (or code we plan to have anyway).

But you're very right about the need to semantically split these into separate 
pieces at least on the API level.

Reuse can be achieved internally but should not be exposed to the user.

On Monday, March 23, 2015 09:19:13 Heiko W.Rupp wrote:
> On 20 Mar 2015, at 17:23, Lukas Krejci wrote:
> > Isn't metrics going to store "events" eventually, too? Those would be
> > textual,
> > wouldn't they?
> > 
> > Also, IMHO, even config could be stored in metrics. Even though that
> > is a bit
> > of a stretch, configuration is after all a time series of structured
> > data...
> 
> If so, would we need to rename this to Hawkular-storage (?) :-)
> 
> Seriously, I think we should consider better decoupling the actual
> storage from
> api and semantics.
> Sounds probably pretty strange, so let me explain:
> If we consider everything a "metric" we are sucking in more and more
> dependencies into metrics or vice versa. But in fact (and we are seeing
> it with the availability discussion), items like availability / computed
> resource state,
> inventory data, ... have a semantic that differs a lot from metrics.
>
> We may still want to store all that in Cassandra, but not necessarily in
> the
> same place inside it. And even less have one api "POST /stuff" where
> people
> throw everything at, but rather specialized ones.
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev