WildFly JVM-Level Monitoring: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 5: | Line 5: | ||
=Metrics= | =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. | |||
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: | |||
* [[Memory_Monitoring_and_Management_Platform_MBeans#Memory_MBean|Memory MBean]] | |||
[[Memory_Monitoring_and_Management_Platform_MBeans#Memory_Pool_MBeans|memory pool MBeans]] and [[Memory_Monitoring_and_Management_Platform_MBeans#Memory_Manager_MBeans|memory managers MBeans]], including the [[Memory_Monitoring_and_Management_Platform_MBeans#Garbage_Collector_MBeans|garbage collector memory managers]]. | |||
* Various thread counts obtained from [[ThreadMXBean_Platform_MBean#ThreadCount|Thread MBean]]. | * Various thread counts obtained from [[ThreadMXBean_Platform_MBean#ThreadCount|Thread MBean]]. | ||
Revision as of 13:38, 11 May 2017
Internal
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.
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:
memory pool MBeans and memory managers MBeans, including the garbage collector memory managers.
- Various thread counts obtained from Thread MBean.