Monitoring Data Collection

Monitoring Data

Also refered to as the runtime data that is generated when a process runs. Monitoring data includes CPU use, heap memory, JVM information and statistics information (average response time and access count) related to service access and client invocation.

Service Data Collection

The service data collection takes DefaultMonitorSupporter.start as the access point and builds the monitor instance (The StandardMonitor instances are of the server type by default, which include the StandardMonitorRepository instance and the uavlog instance). The StandardMonitorRepository instance registers with the monitor. A StandardMonitorRepository instance includes multiple MonitorElement instances which are saved in the elemsMap property.

The elemsMap property stores different collection handlers based on different collection objects:

• ServerEndRespTimeCapHandler: collects the response time and the loading count of Server, App and URL.
• JVMStateCapHandler: collects JVM conditions, including heap use, GC count, thread count, CPU and class count.

Client Data Collection

The service data collection takes DefaultClientMonitorSupporter.start as the access point and builds the monitor instance (The StandardMonitor instances are of the client type by default, which include the StandardMonitorRepository instance and the uavlog instance). The StandardMonitorRepository instance registers with the monitor. A StandardMonitorRepository instance includes multiple MonitorElement instances which are saved in the elemsMap property.

The elemsMap property store one colletion handler only:

• ClientRespTimeCapHandler: collects the response time and loading count of the client.