IBM® provided data types for real-time runtime metrics collection
When you use real-time runtime metrics collection, you must specify the Apache Kafka server topic for each data type in the runtime metrics collection properties file to indicate which topic the data is sent to. The data types are continuous data collection (CDC), name-value pair collection, and Java™ virtual machine (JVM).
For example, you can specify the ServerAnalysisTopic1 Apache Kafka server topic for the SYSTEM_MESSAGES and SYSTEM_LISTS CDC data types, and the ServerAnalysisTopic3 Apache Kafka server topic for the CDC_TAPE data type.
Supported CDC data types
Some CDC data types that you specify on the ZRTMC command create multiple types of data to be sent to Apache Kafka, for example VFA summary and VFA subsystem data. In these instances, you can specify separate Kafka topics for each type of data that is created.
The following table lists the supported CDC data types and the corresponding CDC data types in the runtime metrics collection properties file for specifying Kafka topics.
| CDC data types specified on the ZRTMC and ZCDCO commands | Corresponding CDC data types in the runtime metrics collection properties file for specifying Kafka topics | Default frequencies of the CDC data types specified on the ZRTMC command |
|---|---|---|
| CDC_CHANNEL_UTILIZATION | CHL_UTILIZATION | 5 |
| ENH_CHL_UTILIZATION | ||
| CDC_COMMON_DEPLOY_FILES | COMMON_DEPLOY_FILES | 5 |
| CDC_DASD_DEVICE | DASD_DEVICES | 5 |
| CDC_DASD_METRICS | DASD_METRICS | 0 |
| CDC_DASD_POOL | DASD_POOLS | 5 |
| CDC_DASD_SERVICE_TIME | DASD_SERVICE_TIME | 5 |
| CDC_ISTREAM | ISTREAM | 1 |
| CDC_JAM | SERVICE_JAM | 5 |
| CDC_LODIC | LODIC | 5 |
| CDC_LODIC_UTILIZATION_CLASS | LODIC_UTIL_CLASS | 5 |
| CDC_LPAR_UTILIZATION | LPAR_UTILIZATION | 5 |
| CDC_MPIF | MPIF | 5 |
| CDC_MQ_CHANNEL | MQ_CHL_DETAIL | 5 |
| CDC_MQ_QUEUE | MQ_Q_DETAIL | 5 |
| CDC_MQ_SUMMARY | MQ_SUMMARY | 5 |
| CDC_REMOTE_DATA_STORE | REMOTE_DATA_STORE | 5 |
| CDC_SERVICE | SERVICE_APP | 5 |
| CDC_SYSTEM_BLOCK | SYSTEM_BLOCKS | 1 |
| CDC_SYSTEM_LIST | SYSTEM_LISTS | 5 |
| CDC_SYSTEM_MESSAGE | SYSTEM_MESSAGES | 1 |
| CDC_SUBSYSTEM | SUB_SYS_MSGS | 5 |
| SUB_SYS_USER | ||
| CDC_TAPE | TAPE | 5 |
| CDC_TCPIP | TCP_IP | 30 |
| CDC_TPFDF | TPFDF | 0 |
| CDC_TRAD_DB_ENCRYPTION | TRAD_DB_ENCRYPTION | 5 |
| CDC_VFA_DETAIL | VFA_SUBSYSTEM | 5 |
| VFA_SUMMARY | ||
| Any data type | STATIC_SYS_INFO1 | |
|
Note:
|
||
Supported name-value pair collection data types
- nvpcHorizontal
- nvpcVertical
Supported name-value pair distribution sample collection data types
For name-value pair distribution sample collection, use the TPF_NVP_DIST_SAMPLES data type in the runtime metrics collection properties file for specifying Kafka topics.
Supported anomaly collection data types
For anomaly collection, use the anomalyData data type in the runtime metrics collection properties file for specifying Kafka topics.
Supported JVM data types
- JVM_CLASSES_DATA
- JVM_CPU_DATA
- JVM_GC_DATA
- JVM_IO_DATA
- JVM_JMX_DATA
- JVM_LOCK_DATA
- JVM_METHODTRACE_DATA
- JVM_THREAD_DATA
- JVM_*
If one of these defined data types is not specified in the properties file, the data with that data type is ignored by runtime metrics collection and not sent to Kafka.
If you specify the JVM_* data type, runtime metrics collection sends undefined JVM data to the Kafka topic that is associated with the JVM_* data type. If you do not specify the JVM_* data type, all undefined JVM data types are ignored by runtime metrics collection and not sent to Kafka.
The following example shows the entries of JVM data types that are specified for the topic field of the kafka section in the runtime metrics collection properties file.
If a JVM_JMX_DATA object is sent to runtime metrics collection, the data is sent to the TPF_JVM_DATA Kafka topic. If a JVM_IO_DATA object is sent to runtime metrics collection, runtime metrics collection ignores the data, because the JVM_IO_DATA data type is not specified in the properties file. If a JVM_UNDEFINED_DATA object is sent to runtime metrics collection, the data is sent to the TPF_UNDEFINED_DATA Kafka topic.
JVM_JMX_DATA: 'TPF_JVM_DATA'
JVM_*: 'TPF_UNDEFINED_DATA'