Re: [Hawkular-dev] wildfly agent: jmx/jolokia and prometheus support
Would it be feasible to remove the jolokia/prometheus libs to thin the
artifact, and just leave the code? And then to use those *unsupported*
endpoints add in some documented libs? A fork is possible but if it
withers and gets out of date it will just be baggage.
Another thought is to fork a version that only does jolokia and
prometheus, and then that swarm agent would be really light.
On 9/30/2016 9:00 AM, John Mazzitelli wrote:
There is a concern that the Hawkular WildFly Agent is bloated with
stuff people aren't really using or are going to use and is going to make maintaining
it more complicated than it needs to be.
So I want to get feedback on the following plan. This is being tracked in JIRA here:
https://issues.jboss.org/browse/HWKAGENT-142
We are going to take out support for JMX/Joloxia and Prometheus managed endpoints. The
agent will only support collecting metrics from "DMR endpoints" (that means
WildFly Servers - either in standalone or domain mode).
Rather than lose the code for the JMX/Jolokia and Prometheus support, we are going to
fork master into a separate branch. If we ever do need to resurrect that code, or someone
wants to build an agent with those features to play around with, we'd have that branch
available.
Thoughts?
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev