PMDAHACLUSTER(1)

💖 PMDAHACLUSTER(1) — the High Availability Cluster PMDA, bestie edition 💖

okay so first things first, this is a page from the General Commands Manual, and the star of the show is pmdahacluster, aka the High Availability Cluster PMDA. yes she's a Performance Co-Pilot girlie. let's get into it 🫶

---

✨ SYNOPSIS ✨

$PCP_PMDAS_DIR/hacluster/pmdahacluster [-D debug]

that's it, that's the whole vibe. one binary, one optional flag. lowkey elegant 💅

---

🌸 DESCRIPTION 🌸

so pmdahacluster is out here collecting metric information so you can monitor Pacemaker based HA Clusters through Performance Co-Pilot. that's the whole mission. no cap.

she pulls her metric data from these components that make up a Pacemaker based HA Cluster:

• Pacemaker
• Corosync
• SBD
• DRBD

and if you want the detailed tea on which metrics are actually available? check the included pmns and helpfile that ship with the PMDA. they're right there, go look 👀

---

🎀 INSTALLATION 🎀

install the HA Cluster PMDA by running the Install script as root:

# cd $PCP_PMDAS_DIR/hacluster
# ./Install

and to uninstall, also as root:

# cd $PCP_PMDAS_DIR/hacluster
# ./Remove

⚠️ important bestie: pmdahacluster is launched by pmcd(1) and should never be executed directly. like, do not. she does not want to be summoned by hand 🙈

the Install and Remove scripts are the ones that notify pmcd when the agent gets installed or removed. so it's all handled, you don't have to go tell anyone anything 💖

---

🦋 FILES 🦋

• $PCP_PMDAS_DIR/hacluster/help — the default help text file for the HA Cluster metrics
• $PCP_PMDAS_DIR/hacluster/Install — the installation script for the pmdahacluster agent
• $PCP_PMDAS_DIR/hacluster/Remove — the undo-installation script for the pmdahacluster agent
• $PCP_LOG_DIR/pmcd/hacluster.log — the default log file where error messages from pmdahacluster end up

---

🌈 PCP ENVIRONMENT 🌈

environment variables with the prefix PCP_ are what parameterize the file and directory names that PCP uses. it's giving config-girlboss energy.

on every installation, the file /etc/pcp.conf holds the local values for these variables. and the $PCP_CONF variable can be used to point at an alternative configuration file instead, as described over in pcp.conf(5). slay 🫶

---

🔥 DEBUGGING OPTIONS 🔥

the -D or --debug option turns on extra diagnostics on stderr to help triage problems. real talk though: that information is sometimes cryptic and is primarily intended to give guidance for developers rather than for end-users. so if you're an end-user and it looks like nonsense, that's not you, that's just how it's built 😭

debug is a comma separated list of debugging options. use pmdbg(1) with the -l option to get a list of the available debugging options and what each one means. go read the list, it's right there ✨

---

👑 SEE ALSO 👑

PCPIntro(1), pmcd(1) and pmstore(1).

---

and that's the whole page bestie, you ate 💅 go monitor those clusters, main character energy only 🌸💖✨

this was Performance Co-Pilot, PCP, and yes — PMDAHACLUSTER(1) — signing off 🎀🦋