<div dir="ltr">Sorry missed that part:<br><br><div class="gmail_extra"><br><div class="gmail_quote">2016-03-23 14:47 GMT+01:00 Matt Wringe <span dir="ltr"><<a href="mailto:mwringe@redhat.com" target="_blank">mwringe@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Having the agent running in an EAP instance be able to monitor other jolokia end points is cool. But I don't really understand why this isn't a more standalone java application. I would think it would be much more useful to be able to have a standalone java agent which could run on the same system which is exposing the jolokia endpoint. Say I am only running Tomcat servers and I don't want to run Wildfly just to be able to gather the metrics from Tomcat.</blockquote><div><br></div><div>A lot of people in the Java community use JMXTrans or embedded JMXTrans to monitor Tomcat. As mentioned previously, JMXTrans can send data to ptrans over the Graphite protocol.<br><br></div><div><mea culpa><br>I have all the setup details and article ready since last summer<br>HWKMETRICS-158 Write an article to explain how to use Metrics + JMXTrans + Grafana to monitor Tomcat application<br>I did not publish because I wanted to create a video and then my attention was brought to other things. It's a shame. I will fix this soon.<br><a href="https://issues.jboss.org/browse/HWKMETRICS-158">https://issues.jboss.org/browse/HWKMETRICS-158</a> <br></div></div></mea culpa><br><br>-- <br><div class="gmail_signature"><div dir="ltr"><div>Thomas Segismont<br></div>JBoss ON Engineering Team<br></div></div>
</div></div>