Hide Forgot
_pcp_ rebased to version 4.1.0 The _pcp_ packages have been upgraded to upstream version of Performace Co-Pilot 4.1.0, which provides a number of bug fixes and enhancements over the previous version: * Added a sized-based interim compression to the `pmlogger_check(1)` script to reduce data volume sizes on systems configured via the `pcp-zeroconf` package. * Daily compressed archive metadata files. * Changed metric labels to first class PCP metric metadata. * Metric help text and labels are now stored in PCP archives. * Added more Linux kernel metrics: virtual machines, TTYs, aggregate interrupt and softirq counters, af_unix/udp/tcp connection (inet/ipv6), VFS locking, login sessions, AIO, capacity per block device, and other. * Performance Metrics Application Programming Interface (PMAPI) and the Performance Metrics Domain Agent (PMDA) API have been refactored, including promotion and deprecation of individual functions. * Added new virtual data optimizer (VDO) metrics to `pmdadm(1)`. * Improved integration with Zabbix agentd service with further low-level-discovery support in the `pcp2zabbix(1)` function. * Added a new PMDA `pmdabcc(1)` for exporting BCC and eBPF trace instrumentation. * Added a new PMDA `pmdaprometheus(1)` to consume metrics from Prometheus end-points.
We've been asked to pull in new PCP Prometheus-related functionality in RHEL 7.6 - a rebase will be the way to go there. This will also tackle the vast majority of open BZs for PCP on 7.6, which are fixed upstream in the pcp-4.x series. We have observed only one (very) minor ABI issue with the Fedora pcp-4.x update several months ago, we do not expect this would realistically affect customers.
OK, I've whittled the list down to 10.
Verified against pcp-4.1.0-4.el7.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:3095