WildFly JVM-Level Monitoring: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
Line 4: Line 4:


=Metrics=
=Metrics=
These metrics are collected directly from the platform MBeans exposed by the JVM that executes the JBoss instance. A JMX connection is required, but the same JMX connection can be used to collect JBoss-level and application-level metrics.


==JVM Memory Metrics==
==JVM Memory Metrics==


These metrics are collected directly from the platform MBeans exposed by the JVM that executes the JBoss instance. A JMX connection is required, but the same JMX connection can be used to collect JBoss-level and application-level metrics.
There is a certain degree of overlap between the information provided by the memory-related platform MBeans and the garbage collection log.
 
Note there is a certain degree of overlap between the information provided by the memory-related platform MBeans and the garbage collection log.


Platform MBeans:
Platform MBeans:

Revision as of 13:42, 11 May 2017

Internal

Metrics

These metrics are collected directly from the platform MBeans exposed by the JVM that executes the JBoss instance. A JMX connection is required, but the same JMX connection can be used to collect JBoss-level and application-level metrics.

JVM Memory Metrics

There is a certain degree of overlap between the information provided by the memory-related platform MBeans and the garbage collection log.

Platform MBeans:


memory pool MBeans and memory managers MBeans, including the garbage collector memory managers.