pcp-collectl(1)

1PCPCOMPAT(1)                General Commands Manual               PCPCOMPAT(1)
2
3
4

NAME

6       PCPCompat,  pcp-collectl, pmmgr, pmwebd - backward-compatibility in the
7       Performance Co-Pilot (PCP)
8

INTRODUCTION

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
15       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
22       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

SAR2PCP

28       The  sar2pcp(1) utility is now deprecated, and will be retired in a fu‐
29       ture version of PCP (v6).  This is being replaced by native support for
30       generating  PCP archives within the tools of the sysstat package (which
31       provides sar itself, as well as the sadf utility which produces PCP ar‐
32       chives via the -l option).
33

PMLOGCONF-SETUP

35       Earlier  versions of PCP (prior to v5.1.1) provided a shell script that
36       was used internally by pmlogconf(1), located in the PCP_BINADM_DIR  di‐
37       rectory,  named  pmlogconf-setup.   This  script has been retired.  The
38       equivalent functionality remains available in  the  unlikely  event  it
39       should be needed via the -s or --setup option to pmlogconf(1).
40
41       The version 1 pmlogconf-setup configuration file format (from IRIX) was
42       also retired in this release, after more than  10  years  of  automatic
43       transition to version 2 format by pmlogconf.
44

PMMGR

46       The  standalone  PCP  daemon  manager  pmmgr  has been retired from PCP
47       v5.2.0 onward.  It was phased out in favour of  the  simpler  pmfind(1)
48       service  for setting up pmie(1) and pmlogger(1) ``farms'' of discovered
49       PCP collector systems with pmfind_check(1).  The new mechanisms,  espe‐
50       cially  when integrated with systemd, require no additional daemons and
51       are better integrated with the pmie  and  pmlogger  service  management
52       used elsewhere in PCP.
53

PCP-COLLECTL

55       The  pcp-collectl  utility  has been superceded by pmrep(1) from PCP v5
56       onward.
57
58       The equivalent of pcp-collectl subsystem reporting is achieved as  fol‐
59       lows:
60
61       pmrep :collectl-sc
62              Processor subsystem view.
63
64       pmrep :collectl-sm
65              Memory subsystem view.
66
67       pmrep :collectl-sd
68              Aggregate disks view.
69
70       pmrep :collectl-sD
71              Per-disk-device view.
72
73       pmrep :collectl-dm-sD
74              Device mapper view.
75
76       pmrep :collectl-sn
77              Network subsystem view.
78

PCP-WEBAPPS

80       The  standalone  web applications packaged with older PCP versions have
81       been  superceded  by  grafana-server(1)  with  the  grafana-pcp  plugin
82       https://github.com/performancecopilot/grafana-pcp.
83
84       This  plugin  provides  an implementation of the Vector application, as
85       well as data sources for pmdabpftrace(1) (bpftrace(8) scripts) and  pm‐
86       series(1) (fast, scalable Redis-based time series analysis).
87

PMWEBD

89       The pmwebd daemon has been superceded by pmproxy(1) from PCP v5 onward.
90
91       By  default,  pmproxy will now listen on both its original port (44322)
92       and the PCP web API port (44323) when the time series support is built.
93
94       pmproxy provides a compatible implementation of  the  live  PMWEBAPI(3)
95       interfaces  used  traditionally  by the Vector web application (see the
96       ``PCP-WEBAPPS'' section).  It also provides extensions to the  original
97       pmwebd  REST  APIs  (such as derived metrics, namespace lookups and in‐
98       stance domain profiles), support for  the  HTTPS  protocol,  and  fast,
99       scalable time series querying using the pmseries(1) REST API and redis-
100       server(1).
101
102       The partial Graphite API emulation provided by pmwebd has not been  re-
103       implemented  -  applications  wishing to use similar services could use
104       the scalable time series REST APIs described on PMWEBAPI(3).
105