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

[Heiko W.Rupp]

On 10 Nov 2015, at 19:09, Lucas Ponce wrote:

> - A standalone use of Hawkular Metrics (mainly for OpenShift).
Which may add alerts in the future, which was the trigger
for this whole discussion.
>
> - Hawkular, a integrated project of several components/subproject 
> (bus,accounts,metrics,alerts,inventory,agent,ui,new ones).
>
> - Hawkular BTM (not sure if this will be consumed as part of Hawkular 
> as add-on, or a variant).

This will for sure add into Hawkular-all at some point in time.

> - Hawkular DataMining module (not sure if this will be consumed as 
> part of Hawkular as add-on, or a variant).

As with BTM - DataMining is about prediction of potential
bad conditions and in the future possibly also about root cause
analysis.


> It happens as our components are decoupled and can be consumed 
> separately, so it could be valid if the same user that is using 
> metrics in standalone can add alerts too to work together, but 
> probably that user is not interested in the full Hawkular solution as 
> it has developed its own security, feeds and inventory frameworks (or 
> any combination).

At the moment this is a SEP to me [1]. We need to
care about that OpenShift thingy and Hawkular-all.


> So, if a user can deploy a metrics.war and alerts.war in the 
> deployments folder on a standard wildfly server, that could be 
> interesting an attractive for everyone (or at least that I think is 
> our main motivation for this discussion).

Which will most possibly be possible when Hawkular is
rebased to WF 10 where we will use the embedded
AMQ-Artemis broker.

> have my conclusion clear: we need to go through Hawkular, not 
> replicating things, or in other words, focus all efforst in a single 
> solution that can be used in several scenarios.

+1

[1] http://hitchhikers.wikia.com/wiki/Somebody_Else's_Problem_field