{
"update_time":"Tue Sep 23 18:18:55 PDT 2014",
"milliseconds_span":300000,
"last":4.192128832E8
},
{
"update_time":"Tue Sep 23 18:23:55 PDT 2014",
"milliseconds_span":300000,
"last":3.864813136E8
},
{
"update_time":"Tue Sep 23 18:27:55 PDT 2014",
"milliseconds_span":240000,
"last":3.847236E8
}
]
}
}
Viewing all controller JVM metrics
Many metrics are not persisted to disk. Some metrics are constant over time, at least for the time
the JVM is online. For example, the maximum amount of heap memory allocated by the operating
system to the JVM does not vary during the lifetime of the JVM. It does not make sense to persist
such values over time because this behavior consumes disk space.
To view all metrics that are tracked by the controller with regard to the JVM, including those that
are also persisted as time-series data:
1.
Create a controller support report.
2.
View the data in the support report under the
jvm-metrics
ID.
jvm-metrics
ID.
More information
“Generating a controller support report” (page 152)
Viewing current metric data using a JMX client
You can use JConsole or another JMX client to connect to the controller's JMX server to view
metric data as it is updated in real time.
Metrics that are viewable using a JMX client
The
jmx
field of the
MetricDescriptor
used to create the
TimeStampedMetric
determines
whether or not the metric can be viewed using a JMX client.
The content exposed for each
TimeStampedMetric
is contingent on the type of
TimeStampedMetric
, but typically the most current values used by the
TimeStampedMetric
are visible as they are updated by the creator of the
TimeStampedMetric
.
Prerequisites
For JMX clients to connect to the JMX server of the controller, the following conditions must be
true:
•
The JMX client must be installed on the same system as the controller.
•
No JMX clients are included with the controller or are among the prerequisites for installing
it; they must be installed separately. For example, to use the JConsole JMX client, the
openjdk-7-jdk
package must be installed on the same system as the controller.
•
The controller must be configured to permit local JMX access.
For more information about using JConsole and configuring local JMX access, see the JConsole
documentation provided by Oracle at:
Viewing all controller JVM metrics
149