[ https://issues.jboss.org/browse/HAWKULARQE-63?page=com.atlassian.jira.plu... ] Matt Mahoney updated HAWKULARQE-63: ----------------------------------- Comment: was deleted (was: From JMazz: The only thing added post-0.28.0.Final was this Java Agent stuff. The Wildfly Agent (the thing you've been testing with) hasn't changed - it should work the same as before. The Java Agent that was introduced should work the same as that WildFly agent except: 1) it is installed via the -javaagent option when launching a JVM, not injected in standalone.xml within WildFly itself 2) it uses its own YAML configuration file rather than XML in the standalone.xml (thought the yaml setting names mimic the XML element/attribute names - e.g. metric-set-dmr, local-dmr, etc). Example yaml files are found here (see the real-config*.yaml ones): https://github.com/hawkular/hawkular-agent/tree/master/hawkular-javaagent... 3) You cannot run Java Agent directly in a Host Controller - but since domain mode isn't supported in this Middleware Manager stuff, I doubt you care about that. Really, other than that, this Java Agent should behave just like the WildFly Agent. That is in theory - in actuality, we'll need testing to find the places that are broken But the pieces that are going to be broke are probably not in the agent directly, but in the Middleware Manager UI that hardcoded some things it expects when the agent is deployed as a WildFly subsystem. We would need to fix those kinds of things.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)