We are actively working on other integration efforts, so we definitely need to look beyond WildFly/EAP.On Mar 30, 2016, at 10:23 AM, Matt Wringe <mwringe@redhat.com> wrote:
----- Original Message -----
From: "Jay Shaughnessy" <jshaughn@redhat.com>
To: hawkular-dev@lists.jboss.org
Sent: Monday, March 28, 2016 10:59:05 AM
Subject: Re: [Hawkular-dev] using hawkular wildfly agent as a custom java agent
I think we should limit ourselves to the Wildfly/EAP agent that we're already
working on, as EAP hosted app monitoring/mgmt is our bread and butter. Past
Except this assumption is not necessarily correct. Hawkular, at least Hawkular-Metrics, is not only being used just for Wildfly/EAP monitoring.
We are using Hawkular-Metrics in OpenShift (https://github.com/openshift/origin-metrics) and there are other potential integration points that are being looking into. If we only want to handle the Wildfly/EAP case, then we really need to take a good look and determine if these other integrations make sense or not. Otherwise we should really start to look beyond just Wildfly/EAP so that these integration can be handled better.