Transfer Form link: https: //www.jianshu.com/p/bfd5785c55a1
Types of |
parameter |
Parameter Description |
Whether monitoring |
Monitoring tools |
Importance |
---|---|---|---|---|---|
JVM |
jvm.memory.max | JVM maximum memory | |||
jvm.memory.committed | JVM available memory | Yes | Display and monitor heap memory and Metaspace | important | |
jvm.memory.used | Used JVM memory | Yes | Display and monitor heap memory and Metaspace | important | |
jvm.buffer.memory.used | JVM memory buffer is used | ||||
jvm.buffer.count | The current number of buffers | ||||
jvm.threads.daemon | JVM Number daemon thread | Yes | Displayed on the monitoring page | ||
jvm.threads.live | Current number of active threads JVM | Yes | Monitoring page displayed; monitoring time reaches the alarm threshold | important | |
jvm.threads.peak | JVM peak number of threads | Yes | Displayed on the monitoring page | ||
jvm.classes.loaded | Load the number of classes | ||||
jvm.classes.unloaded | Number of classes unloaded | ||||
jvm.gc.memory.allocated | GC, the younger generation of allocated memory space | ||||
jvm.gc.memory.promoted | GC, the memory space allocated years old | ||||
jvm.gc.max.data.size | GC, the maximum amount of memory the old age | ||||
jvm.gc.live.data.size | FullGC, the old age memory space | ||||
jvm.gc.pause | GC time-consuming | Yes | Displayed on the monitoring page | ||
Tomcat | tomcat.sessions.created | tomcat has created several session | |||
tomcat.sessions.expired | tomcat number of session has expired | ||||
tomcat.sessions.active.current | tomcat number of active session | ||||
tomcat.sessions.active.max | tomcat maximum number of active session | Yes | Page displayed on the monitor, or exceeds the alarm threshold may be dynamically expansion | important | |
tomcat.sessions.alive.max.second | tomcat maximum number of active session duration | ||||
tomcat.sessions.rejected | After the session exceeds the maximum number of session configuration, rejection | Yes | Displayed on the monitoring page, easy to analyze problems | ||
tomcat.global.error | Total number of errors | Yes | Displayed on the monitoring page, easy to analyze problems | ||
tomcat.global.sent | Bytes sent | ||||
tomcat.global.request.max | request the maximum time | ||||
tomcat.global.request | Frequency and duration of the global request | ||||
tomcat.global.received | Global received frequency and duration | ||||
tomcat.servlet.request | The frequency and duration of the request servlet | ||||
tomcat.servlet.error | The total number of errors occurred servlet | ||||
tomcat.servlet.request.max | servlet request the maximum time | ||||
tomcat.threads.busy | tomcat busy thread | Yes | Displayed on the monitoring page, check whether any threads accordingly rammed live | ||
tomcat.threads.current | tomcat current number of threads (including daemon thread) | Yes | Displayed on the monitoring page | important | |
tomcat.threads.config.max | Configuring the maximum number of threads tomcat | Yes | Displayed on the monitoring page | important | |
tomcat.cache.access | tomcat number of read cache | ||||
tomcat.cache.hit | tomcat number of cache hits | ||||
CPU | system.cpu.count | Number of CPU | |||
system.load.average.1m | load average | Yes | Exceeds the alarm threshold | important | |
system.cpu.usage | System CPU usage | ||||
process.cpu.usage | The current process CPU usage | Yes | Exceeds the alarm threshold | ||
http.server.requests | http request to call the situation | Yes | Display 10 requests the largest, longest URL; the amount of unsolicited statistics 200 | important | |
process.uptime | Application has been running time | Yes | Displayed on the monitoring page | ||
process.files.max | To allow the maximum number of handles | Yes | With the use of handles currently open | ||
process.start.time | Application start time point | Yes | Displayed on the monitoring page | ||
process.files.open | The current number of open handles | Yes | Monitoring usage of file handles, exceeds the threshold alarm |