WildFly JVM-Level Monitoring: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 13: | Line 13: | ||
Platform MBeans: | Platform MBeans: | ||
* [[Memory_Monitoring_and_Management_Platform_MBeans#Memory_MBean|Memory MBean]] | * [[Memory_Monitoring_and_Management_Platform_MBeans#Memory_MBean|Memory MBean]] | ||
* [[Memory_Monitoring_and_Management_Platform_MBeans#Memory_Pool_MBeans|Memory Pool MBeans]] | |||
[[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:54, 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 managers MBeans, including the garbage collector memory managers.
- Various thread counts obtained from Thread MBean.