PMDALUSTERCOMM(1)

💖 PMDALUSTERCOMM 💖

okay so bestie, we're looking at pmdalustrecomm from section 1 of the General Commands Manual — the Lustre filesystem comms performance metrics domain agent, aka a PMDA. yes the name is a mouthful, no we're not renaming it, it's iconic actually 🦋

---

✨ SYNOPSIS ✨

$PCP_PMDAS_DIR/lustrecomm/pmdalustrecomm [-D debug] [-d domain] [-l logfile] [-U username]

---

🌸 DESCRIPTION 🌸

pmdalustrecomm is a Performance Metrics Domain Agent (PMDA) — and what it does is literally extract performance metrics from the Linux procfs filesystem, all about how the various aspects of the Lustre filesystem are doing. she's nosy in the best way 💅

The lustrecomm PMDA exports metrics that are focused on distributed communication in the filesystem — so like, metrics related to timeouts, network drops, send/receive information and route lengths. but that's not all, because she also covers the memory use of some of the Lustre filesystem components. versatile queen 👑

okay so a brief description of the pmdalustrecomm command line options, here we go:

• -d — the performance metrics domain number you put here? it is absolutely crucial that it's unique and consistent. like. crucial crucial. domain has to be different for every PMDA on the one host, and the same domain number should be used for the same PMDA on all hosts. that's the whole rule, no cap 🫶
• -l — location of the log file. by default, a log file named lustrecomm.log gets written in the current directory of pmcd(1) when pmdalustrecomm is started, i.e. $PCP_LOG_DIR/pmcd. and if the log file can't be created or isn't writable? output goes to the standard error instead. she finds a way 💅
• -U — user account under which to run the agent. the default is the unprivileged "pcp" account in current versions of PCP, but in older versions the superuser account ("root") was used by default. glow-up behavior fr fr ✨

---

🎀 INSTALLATION 🎀

so if you want access to the names, help text and values for the lustrecomm performance metrics, do the following as root:

# cd $PCP_PMDAS_DIR/lustrecomm
# ./Install

and if you want to undo the installation (we don't judge, sometimes you gotta ✂️), do the following as root:

# cd $PCP_PMDAS_DIR/lustrecomm
# ./Remove

🚨 important bestie: pmdalustrecomm is launched by pmcd(1) and should never be executed directly. the Install and Remove scripts notify pmcd(1) when the agent is installed or removed — they handle the socializing, you just vibe.

---

🗂️ FILES 🗂️

• $PCP_PMCDCONF_PATH — command line options used to launch pmdalustrecomm
• $PCP_PMDAS_DIR/lustrecomm/help — default help text file for the lustrecomm metrics
• $PCP_PMDAS_DIR/lustrecomm/Install — installation script for the pmdalustrecomm agent
• $PCP_PMDAS_DIR/lustrecomm/Remove — undo installation script for the pmdalustrecomm agent
• $PCP_LOG_DIR/pmcd/lustrecomm.log — default log file for error messages and other information from pmdalustrecomm

---

🌈 PCP ENVIRONMENT 🌈

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

---

🐛 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. it's giving developer-only group chat 😭

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. go get the lore bestie 📜

---

👀 SEE ALSO 👀

PCPIntro(1), pmcd(1), pcp.conf(5) and pcp.env(5).

---

that's the whole page, periodt 💖 this was brought to you by Performance Co-Pilot on PCP, and the page itself is literally titled PMDALUSTERCOMM(1) — go forth and monitor those Lustre comms, bestie 🦋✨💅