PMDADS389(1)

💅 PMDADS389 — the 389 Directory Server PMDA, bestie edition

okay so real quick, before we get into it: this is the manual page for pmdads389 from section 1 of the General Commands Manual. yes it's a whole vibe. let's go 🦋

✨ NAME ✨

pmdads389 — the 389 Directory Server PMDA. that's it, that's the name, she's simple and she's iconic 💖

---

🌸 DESCRIPTION 🌸

so pmdads389 is a Performance Metrics Domain Agent (PMDA, say it with me) and what she does is extract live performance data from a 389 Directory Server instance that's currently running. like, actively running. she's not about stale data, she's about right now 💀✨

and if you wanna know what each individual metric actually means? go read the Red Hat Directory Server Administration Guide, it describes every single one of them. not me paraphrasing that, nope, that's where the lore lives 📖

---

🎀 INSTALLATION 🎀

okay bestie, here's the setup arc. pmdads389 reads an optional configuration file:

• $PCP_PMDAS_DIR/ds389/ds389.conf

and inside that file you can put overridden values (and yes, they're Perl code, so act accordingly 💅) for the settings that get listed at the start of pmdads389.pl. those settings are:

• LDAP server
• bind DN
• bind password
• default search scope
• default search base
• default search filter
• query interval
• List of sources
• List of attributes to display for each source

for a starting point, please use the ds389.conf.example that ships with it. don't rawdog a blank config, that's not the move 🙈

once that's all set up, you can get at the names and values for the 389 DS performance metrics by doing this as root:

# cd $PCP_PMDAS_DIR/ds389
# ./Install

and when you wanna uninstall (breaking up is hard, i know 😭), do this as root:

# cd $PCP_PMDAS_DIR/ds389
# ./Remove

important bestie: pmdads389 gets launched by pmcd(1) — she should never be executed directly. do not run her by hand, she's not that kind of girl. also the Install and Remove scripts are the ones that notify pmcd(1) when the agent has been installed or removed. teamwork, periodt 👑

---

📁 FILES 📁

• $PCP_PMDAS_DIR/ds389/ds389.conf.example — example configuration file for the pmdads389 agent. your starter pack 🎁
• $PCP_PMDAS_DIR/ds389/ds389.conf — configuration file for the pmdads389 agent. the real one, your main character config 👑
• $PCP_PMDAS_DIR/ds389/Install — installation script for the pmdads389 agent. she puts things in place ✨
• $PCP_PMDAS_DIR/ds389/Remove — undo installation script for the pmdads389 agent. she undoes the thing, no cap 🫶
• $PCP_LOG_DIR/pmcd/ds389.log — default log file for error messages from pmdads389. when she's got something to say, she writes it here 📝

---

🌈 PCP ENVIRONMENT 🌈

so environment variables with the prefix PCP_ are what parameterize the file and directory names that PCP uses. every time you install, the file /etc/pcp.conf holds the local values for all those variables. and if you want a different configuration file? you can use the $PCP_CONF variable to specify an alternative one, exactly as described in pcp.conf(5). slay 🔥

---

💜 SEE ALSO 💜

PCPIntro(1), ldapsearch(1), pmcd(1) and ns-slapd(8). go read them, they're all part of the same friend group 🫂

---

and that's the whole page, bestie! this little love letter came to you courtesy of Performance Co-Pilot (that's the source/version, mwah 💋) and it's dated PCP — no literally, that's the date on it. stay hydrated, go monitor something, and remember: never run the agent directly. bye!! 🎀💖✨