PCP-VERIFY(1)

💖 PCP-VERIFY(1) 💖

okay bestie, so this is pcp-verify from the Performance Co-Pilot crew, living in the General Commands Manual section of your terminal, and it is literally the vibe-checker for your PCP installation ✨

---

✨ NAME ✨

pcp-verify — verify aspects of a PCP installation 🫶

---

🌸 SYNOPSIS 🌸

pcp verify [-a archive] [-D debug] [-h host] [-csvV?]

---

🦋 DESCRIPTION 🦋

pcp-verify goes snooping around every little corner of a PCP collector installation and reports back on whether it's actually configured correctly for the modes of operation you wanna run. it's giving inspector. it's giving nosy bestie with a clipboard 💅

by default, pcp-verify checks that PMCD is running and that no agents are in a failed state. that's the baseline, no cap. but you can extend and refine those checks with the command line options, so slay, customize away 👑

---

💅 OPTIONS 💅

here's the lineup of command line options, bestie:

• -a archive, --archive=archive — use archive for verification. 📦
• -c, --containers — verify the collector installation for monitoring containers. 🐳
• -h host, --host=host — connect to the PMCD on host for verification. 🖥️
• -s, --secure — verify that the required components for encrypted communication are in place. 🔐
• -v, --verbose — increase the verbosity, and report on each check as it is made. in the absence of any issues found, pcp-verify operates silently. 🤫
• -V, --version — display version number and exit. 🏷️
• -?, --help — display usage message and exit. 🙋

---

😭 DIAGNOSTICS 😭

pcp-verify will exit with a non-zero status if it finds anything worth reporting. otherwise? it's silent and returns zero. the strong silent type fr fr 💀

---

🌈 PCP ENVIRONMENT 🌈

environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. on each installation, the file /etc/pcp.conf contains the local values for these variables. the $PCP_CONF variable may be used to specify an alternative configuration file, as described in pcp.conf(5). 📁

for environment variables affecting PCP tools, see pmGetOptions(3). 👀

---

🎀 DEBUGGING OPTIONS 🎀

the -D or --debug option enables the output of additional diagnostics on stderr to help triage problems — although ngl, the information is sometimes cryptic and primarily intended to provide guidance for developers rather than for end-users 🙈

debug is a comma separated list of debugging options. use pmdbg(1) with the -l option to obtain a list of the available debugging options and their meaning. 🧚

bestie heads up: this debug output was never meant for you, it was meant for the devs. it's still useful, just... expect lore, not clarity 💀

---

👑 SEE ALSO 👑

PCPIntro(1) and pcp(1). 🫶

---

Performance Co-Pilot · PCP · PCP-VERIFY(1) — that's the whole page, source and version tag included, straight from the PCP squad. go verify something, you icon 💖✨🦋