DataBot Metric Reference: Difference between revisions
| (19 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=Internal= | =Internal= | ||
* [[ | * [[DataBot_User_Manual#Metric_Reference|DataBot User Manual]] | ||
= | =Overview= | ||
= | Metric definition fundamentals are available in: <span id='events-api_Metric_Definitions'></span>{{Internal|Events-api_Concepts#Metric_Definition|events-api Metric Definitions}} | ||
Metric source fundamentals are available in: {{Internal|Events-api_Concepts#Metric_Source|events-api Metric Sources}} | |||
= | =Platform Metrics= | ||
< | {{Internal|events OS Metrics|events OS Metrics}} | ||
=JMX Metrics= | |||
<font color=red>TODO</font> | |||
The order in which the key/value pairs are specified in the JMX ObjectName is not relevant. | |||
=JBoss CLI Metrics= | |||
<font color=red>TODO REVIEW</font> | |||
DataBot 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 DataBot process has to be collocated with the JBoss controller on the same host. Support for [[DataBot#n3jHG32|password externalization]] will be implemented in the future. | |||
Syntax: | Syntax: | ||
| Line 30: | Line 40: | ||
</pre> | </pre> | ||
==Types== | |||
JBoss CLI attributes are typed, the controller knows and sends the correct type back. | JBoss CLI attributes are typed, the controller knows and sends the correct type back. DataBot uses the type to build typed Property instances. | ||
==Classpath== | |||
The JBoss CLI client requires specific libraries added to the | The JBoss CLI client requires specific libraries added to the DataBot classpath, and instead of shipping those libraries with the installation bundle, DataBot must be configured to detect and use the libraries from a JBoss instance it has access to. In order to enable DataBot to build the classpath fragment, <tt>jboss_home</tt> must be specified in the configuration file. Example: | ||
<pre> | <pre> | ||
Latest revision as of 15:10, 22 September 2017
Internal
Overview
Metric definition fundamentals are available in:
Metric source fundamentals are available in:
Platform Metrics
JMX Metrics
TODO
The order in which the key/value pairs are specified in the JMX ObjectName is not relevant.
JBoss CLI Metrics
TODO REVIEW
DataBot 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 DataBot 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. DataBot uses the type to build typed Property instances.
Classpath
The JBoss CLI client requires specific libraries added to the DataBot classpath, and instead of shipping those libraries with the installation bundle, DataBot must be configured to detect and use the libraries from a JBoss instance it has access to. In order to enable DataBot to build the classpath fragment, jboss_home must be specified in the configuration file. Example:
... jboss_home=/usr/jboss ...