Yeah, I was under the impression that metrics needs to be handled in a special manner
since we need to run it differently in OpenShift. Which means when we also add in Alerting
to OpenShift, it will also need to be handled in a special manner.
But I guess we can figure that part out when we actually need to add in Alerting.
I think the discussion was also thinking about doing things in a modular manner, where we
could have the different components running as individual containers in kubernetes, and
then spin up (or down) more containers as needed. But it looks like the decision is to not
to go with that approach for scaling the main Hawkular server.
----- Original Message -----
From: "Heiko W.Rupp" <hrupp(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Thursday, May 21, 2015 9:27:19 AM
Subject: Re: [Hawkular-dev] Hawkular integration
On 21 May 2015, at 13:50, Michael Burman wrote:
> it's a good combo to keep those two as "standalone", as there are
> other alerting components available also (such as Bosun) - which we
> would probably like to 'compete' with.
Question is though how much we need to take care of this now and not
address it when we need it.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev