Jolokia2 Agent Telegraf Input Plugin

Use This InfluxDB Integration for Free

Jolokia is an agent that connects clients with Java Management Extensions (JMX) using HTTP. You can use JMX to control and monitor objects called MBeans, which can be devices, applications, and more. Jolokia communicates with a client over HTTP, sending the request and response payloads in JSON. It’s an alternative to JSR-160 connectors and includes additional features such as bulk requests and fine-grained security policies.

Why use the Jolokia2 Telegraf Plugin?

The Jolokia2 Agent Telegraf Input Plugin lets you read JMX metrics from one or more Jolokia agent REST endpoints. The specific metrics you read will depend on what kind of MBean object you are managing. For example, if you are using Jolokia to monitor a message broker, you might collect metrics like queue size, customer count, and memory limit. This Telegraf plugin collects this data so you can easily have it all in one place ready to analyze. This makes managing MBean objects with Jolokia simple and efficient.

How to monitor using the Jolokia2 Telegraf Plugin

To use the Jolokia2 Agent Telegraf Input Plugin, you first need to configure the URL to the Jolokia agent. Then, for each metric, you need to configure name, mbean, and paths. You can use wildcards with the mbean key to collect data for multiple MBeans with one statement. The paths key is a list of MBean attributes to read. Additional optional keys include tag_keys, tag_prefix, field_name, and field_prefix. There’s also an option to configure the Transport Layer Security (TLS) if you’re using encrypted communication. This plugin captures metrics from Jolokia agents so you can manage and monitor MBeans in Telegraf.

Key Jolokia2 Agent metrics to use for monitoring

You can collect a wide variety of metrics with the Jolokia2 Agent. These will vary depending on your system and what you’re monitoring. Some important metrics may include, but are not limited to:

  • Operating System
    • ProcessCpuLoad
    • SystemLoadAverage
    • SystemCpuLoad
  • jvm_runtime
    • Uptime
  • jvm_memory
    • HeapMemoryUsage
    • NonHeapMemoryUsage
    • ObjectPendingFinilizationCount
  • jvm_garbage_collector
    • CollectionTime
    • CollectionCount
  • jvm_memory_pool
    • Usage
    • PeakUsage
    • CollectionUsage
For more information, please check out the documentation.

Project URL   Documentation

Related resources


The most powerful time series
database as a service

Get Started for Free

Developer Education

Training for time series app developers.

View All Education