In the IBM Z Common Data Provider version 2.1.0, the Log Forwarder is enhanced with the capability to collect RMF Monitor III CPC (Central Processor Complex) capacity report.
The CPC capacity report provides the capability to monitor values that are relevant to software pricing as well as partition related processor activities. With this CPC capacity report, you can compare the defined capacity limits against the actual MSU consumption for all partitions of the CPC. In addition, the report contains MSU information generated in the last four hours for the partition on which RMF is running, which clearly shows if the defined capacity limit is appropriate to the workload running on this partition or if WLM has to cap this partition’s workload because the defined limit was set too low.
The report data is retrieved from the RMF Distributed Data Server (DDS). The Log Forwarder converts the data to CSV format and sends them to the Data Streamer. Then the data can be streamed to the analytics platforms (like Elastic Stack or Splunk).
Figure 1 shows the CPC capacity report in RMF.
Figure 2 shows the CPC capacity report data that are collected in Elastic Stack.
Figure 3 shows the CPC capacity report data that are collected in Splunk.
To collect RMF Monitor III CPC capacity report, the main tasks you will need to do include:
- Configure the RMF Distributed Data Server (DDS).
- Grant the Log Forwarder user ID access to generate PassTicket when accessing the RMF Distributed Data Server (DDS).
- In the Configuration Tool, create a policy with the RMF_CPC data stream selected.
The CPC capacity report is the first RMF Monitor III report that is supported by IBM Z Common Data Provider. Other RMF Monitor III reports will be supported over time.
A detailed step-by-step guidance on how to configure the RMF Distributed Data Server for collecting RMF Monitor III reports can be found here:
For additional information on whatâ€™s new in the IBM Z Common Data provider 2.1.0, see: