The Red Hat Ecosystem Catalog is the official source for discovering and learning more about the Red Hat Ecosystem of both Red Hat and certified third-party products and services.
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.
Performance Co-Pilot (PCP) is a system performance analysis toolkit.
$ podman run -d \
--name pcp \
--systemd always \
-p 44321:44321 \
-p 44322:44322 \
-v pcp-archives:/var/log/pcp/pmlogger \
registry.redhat.io/rhel9/pcp
Note: On SELinux enabled systems, the following boolean needs to be set: sudo setsebool -P container_manage_cgroup true
$ sudo podman run -d \
--name pcp \
--privileged \
--net host \
--systemd always \
-e HOST_MOUNT=/host \
-v pcp-archives:/var/log/pcp/pmlogger \
-v /:/host:ro,rslave \
registry.redhat.io/rhel9/pcp
$ docker run -d \
--name pcp \
-p 44321:44321 \
-p 44322:44322 \
-v pcp-archives:/var/log/pcp/pmlogger \
-v /sys/fs/cgroup:/sys/fs/cgroup:ro \
registry.redhat.io/rhel9/pcp
Note: On SELinux enabled systems, the following boolean needs to be set: sudo setsebool -P container_manage_cgroup true
$ sudo docker run -d \
--name pcp \
--privileged \
--net host \
-e HOST_MOUNT=/host \
-v pcp-archives:/var/log/pcp/pmlogger \
-v /:/host:ro,rslave \
-v /sys/fs/cgroup:/sys/fs/cgroup:ro \
registry.redhat.io/rhel9/pcp
PCP_SERVICESDefault: pmcd,pmie,pmlogger,pmproxy
Comma-separated list of PCP services to start.
HOST_MOUNTDefault: unset.
Path inside the container to the bind mount of / on the host.
REDIS_SERVERSDefault: localhost:6379
Redis connection spec(s) - could be any individual cluster host, and all hosts in the cluster will be automatically discovered. Alternately, use comma-separated hostspecs (non-clustered setup)
For custom configuration options beyond the above environment variables, it is advised to use a bind mount with a configuration file on the host to the container. Example command to run a pmlogger-only container:
$ podman run -d \
--name pmlogger \
--systemd always \
-e PCP_SERVICES=pmlogger \
-v $(pwd)/pmlogger.control:/etc/pcp/pmlogger/control.d/local:z \
-v pcp-archives:/var/log/pcp/pmlogger \
registry.redhat.io/rhel9/pcp
pmlogger.control:
$version=1.1
remote.pmcdhost.corp n n PCP_ARCHIVE_DIR/remote_pmcd -N -r -T24h10m -c config.default -v 100Mb
/var/log/pcp/pmloggerPerformance Co-Pilot archive files with historical metrics.
44321/tcpThe pmcd daemon listens on this port and exposes the PMAPI(3) to access metrics.
44322/tcpThe pmproxy daemon listens on this port and exposes the REST PMWEBAPI(3) to access metrics.
The following information was extracted from the containerfile and other sources.
| Summary | Performance Co-Pilot |
| Description | Performance Co-Pilot is a system performance analysis toolkit. |
| Provider | Red Hat |
| Maintainer | PCP Maintainers <pcp-maint@redhat.com> |
The following information was extracted from the containerfile and other sources.
| Repository name | rhel9/pcp |
| Image version | 6 |
| Architecture | amd64 |
| Usage | podman run -d --name pcp --systemd always -p 44321:44321 -p 44322:44322 -v pcp-archives:/var/log/pcp/pmlogger registry.redhat.io/rhel9/pcp |
| Exposed ports | 44321:pmcd 44322:pmproxy |
Use the following instructions to get images from a Red Hat container registry using registry service account tokens. You will need to create a registry service account to use prior to completing any of the following tasks.
First, you will need to add a reference to the appropriate secret and repository to your Kubernetes pod configuration via an imagePullSecrets field.
Then, use the following from the command line or from the OpenShift Dashboard GUI interface.
Use the following command(s) from a system with podman installed
Use the following command(s) from a system with docker service installed and running
Use the following instructions to get images from a Red Hat container registry using your Red Hat login.
For best practices, it is recommended to use registry tokens when pulling content for OpenShift deployments.
Use the following command(s) from a system with podman installed
Use the following command(s) from a system with docker service installed and running
Source code is available for all Red Hat UBI-based images in the form of downloadable containers. Here are a few things you should know about Red Hat source containers.
Use skopeo to copy the source image to a local directory
Inspect the image
Untar the contents
Begin examining and using the content.