DataBot Metric Reference

Internal

• os-stats

Metrics

Platform Metrics

• PhysicalMemoryTotal (GitHub)
• PhysicalMemoryFree (GitHub)
• PhysicalMemoryUsed (GitHub)

JBoss CLI Metrics

os-stats can be configured to read CLI metrics from JBoss controllers. The controller is identified by its host, port and username controller components. If none of these are explicitly specified, the localhost:9999 and local authentication are assumed, which means the os-stats process has to be collocated with the JBoss controller on the same host. Support for password externalization will be implemented in the future.

Syntax:

jboss:[[username:password@]host[:port]]/path-element-1/path-element-2/attribute-name

Example:

jboss:/subsystem=infinispan/cache-container=clustered/distributed-cache=web/number-of-entries
jboss:localhost/subsystem=infinispan/cache-container=clustered/distributed-cache=web/number-of-entries
jboss:localhost:9999/subsystem=infinispan/cache-container=clustered/distributed-cache=web/number-of-entries
jboss:test:test123@localhost:9999/subsystem=infinispan/cache-container=clustered/distributed-cache=web/number-of-entries

Types

JBoss CLI attributes are typed, the controller knows and sends the correct type back. os-stats uses the type to build typed Property instances.

Classpath

The JBoss CLI client requires specific libraries added to the os-stats classpath, and instead of shipping those libraries with the installation bundle, os-stats must be configured to detect and use the libraries from a JBoss instance is has access to. In order to enable os-stats to build the classpath fragment, jboss_home must be specified in the configuration file. Example:

...
jboss_home=/usr/jboss
...