Wild-fly logo

JBoss Wildfly Monitoring Template

Telegraf Plugins used:

Included Resources:

  • 1 Telegraf Configuration: 'jboss-wildfly-config'
  • 1 Dashboards: 'jboss-wildfly'
  • 1 Label: 'jboss-wildfly'
  • 1 Bucket: 'jboss-wildfly'

Quick Install

If you have your InfluxDB credentials configured in the CLI, you can install this template with:

https://raw.githubusercontent.com/influxdata/community-templates/master/jboss_wildfly/jboss_wildfly.yml

Wildfly, formerly known as JBoss, is an open source application server originally authored by JBoss and now maintained by RedHat.

Why JBoss monitoring?

To ensure that your applications work as you developed them to and deliver a great user experience, monitoring application performance is key. If your application is using JBoss to build, deploy and host your Java- based applications, then ensuring the performance of JBoss is necessary. This can be done by collecting and analyzing JBoss metrics using the Jolokia2 Telegraf plugin.

The JBoss Wildfly Monitoring Template provides information about your JBoss Wildfly instance, including metrics such as Uptime, CPU Usage, Heap Memory, Non Heap Memory, Memory Pool Collections, Networking and Disk IO.

JBoss Wildfly monitoring dashboard

How to use JBoss Wildfly Monitoring Template

Once your InfluxDB credentials have been properly configured in the CLI, you can install the JBoss Wildfly Monitoring Template using the Quick Install command. Once installed, the data for the dashboard will be populated by the included Telegraf configuration, which contains the relevant Jolokia2 Telegraf Input. Note that you might need to customize the input configuration to better serve your needs, including by specifying a new input value. All of this will depend on how your organization currently runs JBoss Wildfly.

To find out more information about environmental variables within the Telegraf configuration, consult the following link.

Key JBoss Wildfly monitoring metrics to monitor

Some of the most important JBoss Wildfly monitoring metrics that you should proactively monitor include:

  • Uptime
  • CPU Usage
  • System Load
  • System RAM Usage
  • Processes running
  • Heap Memory Usage
  • Memory Pool Collection
  • Memory Pool Peak
  • Request rate
    • Network (bytes) received
    • Network (bytes) sent
  • Network error rates
  • Garbage Collection
  • Disk IO time
  • Disk IO reads and writes

Related Resources

MongoDB Monitoring Template

Monitor your MongoDB instance in order to determine the current state of your database.

Apache HTTP Server Telegraf Plugin

Learn how to monitor Apache HTTP Server using the Telegraf plugin.

Redis Monitoring Template

Check out the Redis Monitoring Template to keep your applications up and running.

Scroll to Top