1PCPCOMPAT(1) General Commands Manual PCPCOMPAT(1)
2
6 PCPCompat, pcp-collectl, pmmgr, pmwebd - backward-compatibility in the
7 Performance Co-Pilot (PCP)
8
10 The Performance Co-Pilot (PCP) is a toolkit designed for monitoring and
11 managing system-level performance. These services are distributed and
12 scalable to accommodate the most complex system configurations and per‐
13 formance problems.
14 In order to achieve these goals effectively, protocol and on-disk com‐
16 patibility is provided between different versions of PCP. It is feasi‐
17 ble (and indeed encouraged) to use current PCP tools to interrogate any
18 remote, down-rev or up-rev pmcd(1) and also to replay any historical
19 PCP archive (the PCP testsuite includes PCP archives created over 20
20 years ago!).
21 From time to time the PCP developers deprecate and remove PCP utili‐
23 ties, replacing them with new versions of utilities providing compara‐
24 ble features. This page describes replacement utilities for historical
25 PCP tools.
26
28 Earlier versions of PCP (prior to v5.1.1) provided a shell script that
29 was used internally by pmlogconf(1), located in the PCP_BINADM_DIR
30 directory, named pmlogconf-setup. This script has been retired. The
31 equivalent functionality remains available in the unlikely event it
32 should be needed via the -s or --setup option to pmlogconf(1).
33 The version 1 pmlogconf-setup configuration file format (from IRIX) was
35 also retired in this release, after more than 10 years of automatic
36 transition to version 2 format by pmlogconf.
37
39 The standalone PCP daemon manager pmmgr has been retired from PCP
40 v5.2.0 onward. It was phased out in favour of the simpler pmfind(1)
41 service for setting up pmie(1) and pmlogger(1) ``farms'' of discovered
42 PCP collector systems with pmfind_check(1). The new mechanisms, espe‐
43 cially when integrated with systemd, require no additional daemons and
44 are better integrated with the pmie and pmlogger service management
45 used elsewhere in PCP.
46
48 The pcp-collectl utility has been superceded by pmrep(1) from PCP v5
49 onward.
50 The equivalent of pcp-collectl subsystem reporting is achieved as fol‐
52 lows:
53 pmrep :collectl-sc
55 Processor subsystem view.
56 pmrep :collectl-sm
58 Memory subsystem view.
59 pmrep :collectl-sd
61 Aggregate disks view.
62 pmrep :collectl-sD
64 Per-disk-device view.
65 pmrep :collectl-dm-sD
67 Device mapper view.
68 pmrep :collectl-sn
70 Network subsystem view.
71
73 The standalone web applications packaged with older PCP versions have
74 been superceded by grafana-server(1) with the grafana-pcp plugin
75 https://github.com/performancecopilot/grafana-pcp.
76 This plugin provides an implementation of the Vector application, as
78 well as data sources for pmdabpftrace(1) (bpftrace(8) scripts) and
79 pmseries(1) (fast, scalable Redis-based time series analysis).
80
82 The pmwebd daemon has been superceded by pmproxy(1) from PCP v5 onward.
83 By default, pmproxy will now listen on both its original port (44322)
85 and the PCP web API port (44323) when the time series support is built.
86 pmproxy provides a compatible implementation of the live PMWEBAPI(3)
88 interfaces used traditionally by the Vector web application (see the
89 ``PCP-WEBAPPS'' section). It also provides extensions to the original
90 pmwebd REST APIs (such as derived metrics, namespace lookups and
91 instance domain profiles), support for the HTTPS protocol, and fast,
92 scalable time series querying using the pmseries(1) REST API and redis-
93 server(1).
94 The partial Graphite API emulation provided by pmwebd has not been re-
96 implemented - applications wishing to use similar services could use
97 the scalable time series REST APIs described on PMWEBAPI(3).
98
100 pcp(1), pmcd(1), pmrep(1), pmfind(1), pmfind_check(1), pmlogconf(1),
101 pmproxy(1), pmseries(1), pmdabpftrace(1), redis-server(1), grafana-
102 server(1) and PMWEBAPI(3).
103Performance Co-Pilot PCP PCPCOMPAT(1)