7.154. pcp

Bug Fixes

BZ#1158681

New kernel metrics: memory, vCPU, device mapper, nfs4.1 operations, more per-cgroup metrics

• New Performance Metrics Domain Agents (PMDA): NVIDIA, Linux, 389 Directory Server, hardware event counters, CIFS, activeMQ
• New vCPU and MemAvailable pmchart views
• New pmiostat, pcp-dmcache, pcp2graphite, ganglia2pcp tools
• Nanosecond resolution event timestamps
• The pmParseUnitsStr() function added to the Performance Metrics Application Programming Interface (PMAPI)
• ACAO header JSON responses added to the Performance Metrics Web Daemon (pmwebd)
• The "ruleset" extensions to the pmie language
• Support for Python v3 and Python API extensions
• Support for xz compression for daily archives
• Support for long form of command-line options
• Support for active service probing in libpcp
• Support for new sysstat versions and sar2pcp fixes
• Direct support for PCP archive in the pmatop utility

BZ#1196540

Previously, on IBM S/390 platforms, unanticipated formatting in the /proc/cpuinfo file negatively affected the PCP Linux kernel PMDA. As a consequence, the agent terminated unexpectedly with a segmentation fault when accessing certain processor related performance metrics. This update fixes parsing of /proc/cpuinfo for IBM S/390, and all PCP processor metrics are now fully functional and robust on this platform.

BZ#1131022

Previously, the PCP pmlogger daemon start script started the daemon only if the pmlogger service was enabled by the "chkconfig on" command. Consequently, the daemon silently failed to start when the service was disabled. With this update, additional diagnostics have been added to the start script. Now, when attempting to start the pmlogger daemon with the pmlogger service disabled, the user is properly informed and given instructions on how to eliminate the problem.