Bug 1423020
| Summary: | rebase pcp for rhel7.4 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Dave Brolley <brolley> |
| Component: | pcp | Assignee: | Nathan Scott <nathans> |
| Status: | CLOSED ERRATA | QA Contact: | Miloš Prchlík <mprchlik> |
| Severity: | low | Docs Contact: | Vladimír Slávik <vslavik> |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | brolley, fche, lberk, mbenitez, mcermak, mgoodwin, mprchlik, nathans |
| Target Milestone: | rc | Keywords: | Rebase |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | pcp-3.11.8-1.el7 | Doc Type: | Rebase: Bug Fixes and Enhancements |
| Doc Text: |
_pcp_ rebased to version 3.11.8
The *Performance Co-Pilot* application (PCP) has been upgraded to upstream version 3.11.81, which provides a number of bug fixes and enhancements over the previous version. Notable enhancements include:
* A new client tool *pcp2influxdb* has been added to allow export of performance metric values to the *influxdb* database.
* New client tools *pcp-mpstat* and *pcp-pidstat* have been added to allow retrospective analysis of mpstat and pidstat values.
* New performance metrics have been added for device mapper, *Ceph* devices, cpusched cgroups, per-processor soft IRQs, *buddyinfo*, *zoneinfo*, shared memory, *libvirt*, same-page-sharing, *lio*, *Redis*, and *Docker*.
* Additional performance metrics from several subsystems are now available for a variety of PCP analysis tools.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 18:29:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dave Brolley
2017-02-16 21:36:58 UTC
Meant rhel7.4 above, of course Verified with build pcp-3.11.8-7.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-2017:1968 |