http:\/\/jboss01.example.com:8080\/jolokia\/<\/a> that Jolokia is deployed. The response will return some basic information about Jolokia as JSON.<\/p>\nNext we’ll need to install collectd, a general monitoring agent which can retrieve monitoring data from many services through its plugins. We will install collectd and the JSON-curl plugin which is needed to read the data from Jolokia on jboss01.example.com. In Fedora Linux this can be done with<\/p>\n
\nyum install collectd collectd_json-curl
\nsystemctl enable collectd
\n<\/code><\/p>\nBefore we start the collecd agent we need some configuration. In \/etc\/collectd.conf you need to enable the plugins for graphite and curl_json.<\/p>\n
\n#
\n# Config file for collectd(1).
\n# Please read collectd.conf(5) for a list of options.
\n# http:\/\/collectd.org\/
\n#
\n...
\nLoadPlugin curl_json
\n...
\nLoadPlugin write_graphite
\n...
\n<Plugin write_graphite>
\n <Node \"jboss01\">
\n Host \"graphite.example.com\"
\n Port \"2003\"
\n Protocol \"tcp\"
\n LogSendErrors true
\n# Prefix \"collectd\"
\n# Postfix \"collectd\"
\n# StoreRates true
\n# AlwaysAppendDS false
\n# EscapeCharacter \"_\"
\n <\/Node>
\n<\/Plugin>
\n...
\nInclude \"\/etc\/collectd.d\"
\n<\/code><\/p>\nand for specifying the JMX values which we want to monitor we set up a new file \/etc\/collectd.d\/wildfly.conf with <\/p>\n
\n<Plugin curl_json>
\n <URL \"http:\/\/jboss01.example.com:8080\/jolokia\/read\/java.lang:type=Memory\">
\n Instance \"Memory\"
\n <Key \"value\/NonHeapMemoryUsage\/*\">
\n Type \"memory\"
\n <\/Key>
\n <Key \"value\/HeapMemoryUsage\/*\">
\n Type \"memory\"
\n <\/Key>
\n <\/URL>
\n <URL \"http:\/\/jboss01.example.com:8080\/jolokia\/read\/java.lang:type=Threading\/ThreadCount\">
\n Instance \"ThreadCount\"
\n &;ltKey \"value\">
\n Type \"gauge\"
\n <\/Key>
\n <\/URL>
\n <URL \"http:\/\/jboss01.example.com:8080\/jolokia\/read\/java.lang:type=OperatingSystem\/OpenFileDescriptorCount\">
\n Instance \"OpenFiles\"
\n <Key \"value\">
\n Type \"gauge\"
\n <\/Key>
\n <\/URL>
\n <URL \"http:\/\/jboss01.example.com:8080\/jolokia\/read\/jboss.as:subsystem=datasources,data-source=ExampleDS,statistics=pool\">
\n Instance \"ExampleDS\"
\n <Key \"value\/ActiveCount\">
\n Type \"gauge\"
\n <\/Key>
\n <Key \"value\/AvailableCount\">
\n Type \"gauge\"
\n <\/Key>
\n <\/URL>
\n<\/Plugin>
\n<\/code><\/p>\nThe syntax is pretty straightforward. Each JMX bean you want to query is specified with the URL with which it will be retrieved from Jolokia. Each attribute from the JSON result set is defined by the Key. You can use wildcards within the keys. This example retrieves the JVM parameters for Memory, Threads and Open Files as well as the key values of the DataSource ExampleDS. If you want to monitor different values you need to provide the name of the JMX bean. jvisualvm is a great tool to inspect JMX beans. JBoss Wildfly provides a lot of JMX beans out of the box (e.g. for JMS queues) and if you enable the statistics for EJBs, Transactions, Servlets etc. all of those can be retrieved like this. You can also write your own JMX beans and deploy it with your application code.<\/p>\n
Now you can start the collectd service with<\/p>\n
systemctl start collectd<\/code> <\/p>\nand should the the values appear at jboss01_example_com.curl_json-INSTANCE, with the name of the instance you have defined in the configuration file above.<\/p>\n","protected":false},"excerpt":{"rendered":"
Once you have a running Java application server (in production), you are need of some kind of monitoring of the JVM’s main parameter (Memory, Threads), the datasources, queues, calls and different metrics provided by the applications. In this post I’ll show how to set up a monitoring chain for JBoss Wildfly. The main ingredients are […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9,43,36],"tags":[47,24],"class_list":["post-448","post","type-post","status-publish","format-standard","hentry","category-java","category-jboss-as7","category-linux","tag-jboss-wildfly","tag-jmx"],"_links":{"self":[{"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=\/wp\/v2\/posts\/448","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=448"}],"version-history":[{"count":5,"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=\/wp\/v2\/posts\/448\/revisions"}],"predecessor-version":[{"id":453,"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=\/wp\/v2\/posts\/448\/revisions\/453"}],"wp:attachment":[{"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=448"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=448"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.johannes-beck.name\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=448"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}