[Hawkular-dev] Hawkular Metrics + Hawkular Alerts - Phase 0

[Thomas Segismont]

Le 10/11/2015 00:33, Stefan Negrea a écrit :
> I never said something is broken. The document is meant to be an iteration over what we have today. More precisely, contains two proposals for moving forward with an unified communication channel. And also there is a proposal for a new feature. I asked for feedback on those two communication methods to adopt one; with the goal to support the newly proposed feature.
>
> The current implementation is not broken for the current use cases (the integration in Hawkular). But that is not the point, and neither did I claim that is broken. It's not about fixing something that is broken but about creating something new. Just one example, a distributed environment with multiple Metrics and Alerts deployments will just not work with what is there today. And that was discussed thoroughly prior to making the document public.
>
> Thomas, you are yet to propose an alternative Phase 1 (or 0); or even changes to the current document.

Stefan I have read the document carefully, I can't give my opinion on a 
plan or propose an alternative if I don't get its fundamental 
motivations. I wish they had been discussed here before any plan is made up.

I am trying to figure out why Hawkular is not the Metrics + Alerts 
integration which is looked for. It seems like a legitimate questioning 
to me, considering:
- the plan described in the document involves creating a new component 
integration mechanism
- the feature used as an illustration is already implemented in Hawkular

 From your last reply, it seems that this fundamental problem is the 
assumption that different component (Metrics, Alerts) and broker 
instances in a distributed environment will not work. Why wouldn't it?

If there are other motivations, I would like to hear them.