telegraf/plugins/inputs/jolokia
Cameron Sparr 0dbb52f9d6 Seems to be a toml parse bug around triple pounds 2016-04-08 18:34:44 +02:00
..
README.md renaming plugins -> inputs 2016-01-07 15:04:30 -07:00
jolokia.go Seems to be a toml parse bug around triple pounds 2016-04-08 18:34:44 +02:00
jolokia_test.go Throughout telegraf, use telegraf.Metric rather than client.Point 2016-01-27 23:47:32 -07:00

README.md

Telegraf plugin: Jolokia

Plugin arguments:

  • context string: Context root used of jolokia url
  • servers []Server: List of servers
    • name string: Server's logical name
    • host string: Server's ip address or hostname
    • port string: Server's listening port
  • metrics []Metric
    • name string: Name of the measure
    • jmx string: Jmx path that identifies mbeans attributes
    • pass []string: Attributes to retain when collecting values
    • drop []string: Attributes to drop when collecting values

Description

The Jolokia plugin collects JVM metrics exposed as MBean's attributes through jolokia REST endpoint. All metrics are collected for each server configured.

See: https://jolokia.org/

Measurements:

Jolokia plugin produces one measure for each metric configured, adding Server's name, host and port as tags.

Given a configuration like:

[jolokia]

[[jolokia.servers]]
  name = "as-service-1"
  host = "127.0.0.1"
  port = "8080"

[[jolokia.servers]]
  name = "as-service-2"
  host = "127.0.0.1"
  port = "8180"

[[jolokia.metrics]]
  name = "heap_memory_usage"
  jmx  = "/java.lang:type=Memory/HeapMemoryUsage"
  pass = ["used", "max"]

The collected metrics will be:

jolokia_heap_memory_usage name=as-service-1,host=127.0.0.1,port=8080 used=xxx,max=yyy
jolokia_heap_memory_usage name=as-service-2,host=127.0.0.1,port=8180 used=vvv,max=zzz