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

NAME

6       PCPCompat, pcp-collectl, pmwebd - backward-compatibility in the Perfor‐
7       mance 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

PCP-COLLECTL

28       The  pcp-collectl  utility  has been superceded by pmrep(1) from PCP v5
29       onward.
30
31       The equivalent of pcp-collectl subsystem reporting is achieved as  fol‐
32       lows:
33
34       pmrep :collectl-sc
35              Processor subsystem view.
36
37       pmrep :collectl-sm
38              Memory subsystem view.
39
40       pmrep :collectl-sd
41              Aggregate disks view.
42
43       pmrep :collectl-sD
44              Per-disk-device view.
45
46       pmrep :collectl-dm-sD
47              Device mapper view.
48
49       pmrep :collectl-sn
50              Network subsystem view.
51

PCP-WEBAPPS

53       The  standalone  web applications packaged with older PCP versions have
54       been  superceded  by  grafana-server(1)  with  the  grafana-pcp  plugin
55       ⟨https://github.com/performancecopilot/grafana-pcp⟩.
56
57       This  plugin  provides  an implementation of the Vector application, as
58       well as data sources  for  pmdabpftrace(1)  (bpftrace(8)  scripts)  and
59       pmseries(1) (fast, scalable Redis-based time series analysis).
60

PMWEBD

62       The pmwebd daemon has been superceded by pmproxy(1) from PCP v5 onward.
63
64       By  default,  pmproxy will now listen on both its original port (44322)
65       and the PCP web API port (44323) when the time series support is built.
66
67       pmproxy provides a compatible implementation of  the  live  PMWEBAPI(3)
68       interfaces  used  traditionally  by the Vector web application (see the
69       ``PCP-WEBAPPS'' section).  It also provides extensions to the  original
70       pmwebd  REST  APIs  (such  as  derived  metrics,  namespace lookups and
71       instance domain profiles), support for the HTTPS  protocol,  and  fast,
72       scalable time series querying using the pmseries(1) REST API and redis-
73       server(1).
74
75       The partial Graphite API emulation provided by pmwebd has not been  re-
76       implemented  -  applications  wishing to use similar services could use
77       the scalable time series REST APIs described on PMWEBAPI(3).
78

SEE ALSO

80       pcp(1), pmcd(1), pmrep(1),  pmproxy(1),  pmseries(1),  pmdabpftrace(1),
81       redis-server(1), grafana-server(1) and PMWEBAPI(3).
82
83
84
85Performance Co-Pilot                  PCP                         PCPCOMPAT(1)
Impressum