WildFly JVM-Level Monitoring: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 14: Line 14:
* [[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]]  (these depend on the JVM version and the type of garbage collector in use).
* [[Memory_Monitoring_and_Management_Platform_MBeans#Memory_Pool_MBeans|Memory Pool MBeans]]  (these depend on the JVM version and the type of garbage collector in use).
* [[Memory_Monitoring_and_Management_Platform_MBeans#Garbage_Collector_MBean|Garbage Collector Memory Manager MBeans]] (these depend on the type of garbage collection in use).
* [[Memory_Monitoring_and_Management_Platform_MBeans#Garbage_Collector_MBeans|Garbage Collector Memory Manager MBeans]] (these depend on the type of garbage collection in use).




* 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 14:22, 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: