PMDADENKI(1)

💖 PMDADENKI 💖

okay bestie, gather round, because this one is literally about how much electricity your machine is out here eating. it's pmdadenki, a manual page from the PCP (Performance Co-Pilot) crew, and it's giving main character energy for power metrics. 💅

---

✨ NAME ✨

pmdadenki — metrics related to the systems electrical consumption

---

🎀 SYNOPSIS 🎀

$PCP_PMDAS_DIR/denki/pmdadenki [-D debug] [-d domain] [-l logfile]

---

🔥 DESCRIPTION 🔥

so pmdadenki is a Performance Metrics Domain Agent (PMDA) — that's the little worker bee that goes out and extracts electricity related performance metrics. that's its whole job. that's the assignment. 👑

right now, the metrics it can pull are:

• stuff from the Running Average Power Limit (RAPL) Intel CPU feature 🖥️
• battery charge values 🔋

...but only if supported by the hardware. so if your box doesn't have the goods, no metrics for you, sorry babe. 🙈

now, about -l — this one sets the Location of the log file. by default, a log file named denki.log gets written in the current directory of pmcd(1) when pmdadenki is started, i.e. $PCP_LOG_DIR/pmcd. and if the log file cannot be created or is not writable? then output is written to the standard error instead. no log file, no problem, we just yell into stderr. 😭

---

🌸 INSTALLATION 🌸

the denki PMDA is installed and available by default on Linux. so like, you already have it, bestie. no cap.

if you wanna undo the installation, do the following as root:

# cd $PCP_PMDAS_DIR/denki
# ./Remove

and if you want to establish access to the names, help text and values for the denki metrics once more, after removal, do the following as root:

# cd $PCP_PMDAS_DIR/denki
# ./Install

⚠️ important: pmdadenki is launched by pmcd(1) and should never be executed directly. it's not a solo artist, it's a group project. the Install and Remove scripts notify pmcd(1) when the agent is installed or removed, so everything stays in sync. 🫶

---

🦋 FILES 🦋

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

---

🌈 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. and plot twist — the $PCP_CONF variable may be used to specify an alternative configuration file, as described in pcp.conf(5). 🧚

---

💀 DEBUGGING OPTIONS 💀

the -D or --debug option enables the output of additional diagnostics on stderr to help triage problems. lowkey though, the information is sometimes cryptic and primarily intended to provide guidance for developers rather than for end-users. don't say we didn't warn you. 🙈

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.

debugging options specific to pmdadenki are as follows:

• appl0 — verbose diagnostics

---

👑 SEE ALSO 👑

PCPIntro(1), pmcd(1), denki/README file, pcp.conf(5) and pcp.env(5).

---

and that's the whole vibe check, bestie. this page came to you straight from the Performance Co-Pilot girlies at PCP — PMDADENKI(1), slay, periodt. 💖✨🎀