[Hawkular-dev] hawkular wildfly agent - jmx - remote and local

[Thomas Heute]

In which case for Fuse it would *not* be on the same JVM ? Is Jolokia part
of Fuse or how would one "set it up" ?

On Wed, Nov 30, 2016 at 12:14 AM, John Mazzitelli <mazz at redhat.com> wrote:

> The Fuse folks asked that we return back the Jolokia/JMX support. So that
> is now in a PR, waiting for final approval before merging:
>
> https://issues.jboss.org/browse/HWKAGENT-151
> https://github.com/hawkular/hawkular-agent/pull/274
>
> In addition, to avoid going over the network to perform Jolokia REST calls
> when the agent and the managed MBeans are in the same VM, I've added a new
> local-jmx managed server. So you can define a local-jmx managed server (and
> still use the same metric-jmx and avail-jmx sets you've defined before for
> the jolokia support) and have inventory and metrics collected for that
> stuff, but it goes over the internal MBeanServerConnection rather than a
> remote Jolokia endpoint. Note that obviously this is only useful if the
> agent is deployed in the same WildFly as where your MBeans are. But the
> point is, you define your JMX resources, avails, and metrics just like
> before - nothign changed there - but instead of using remote-jmx you use
> local-jmx in <managed-servers>
>
> See:
>
> https://issues.jboss.org/browse/HWKAGENT-152
> https://github.com/hawkular/hawkular-agent/pull/275
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20161130/a4f9307a/attachment.html