PMDAUNBOUND(1)

πŸ“¦
version 7.2.2 Β· 2 versions
, in arch rolling, centos-stream 10, centos-stream 9, debian trixie, fedora 43, fedora 44, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’… PMDAUNBOUND(1) β€” like, the General Commands Manual entry, bestie

okay so this is pmdaunbound β€” that's the whole vibe, that's the name, periodt.


✨ NAME ✨

pmdaunbound β€” the Unbound resolver PMDA πŸ¦‹


🌸 DESCRIPTION 🌸

pmdaunbound is a Performance Metrics Domain Agent (PMDA), and what it does is export metric values about the Unbound DNS resolver using the unbound-control(8) stats_noreset command. that's it, that's the job πŸ’–

and the payoff?? it gives you so much insight into query types, response time, cache hits/misses, etc. literally a whole personality reveal for your resolver. if you wanna know what each statistics counter actually means, go read the unbound-control(8) man page β€” it explains every single one, no cap πŸ“–

want even more on the Unbound DNS resolver itself? it lives at https://unbound.net/ β€” go be nosy, you're allowed 🌈


πŸŽ€ INSTALLATION πŸŽ€

install the Unbound PMDA by running the Install script as root:

# cd $PCP_PMDAS_DIR/unbound
# ./Install

and to uninstall, do this as root too:

# cd $PCP_PMDAS_DIR/unbound
# ./Remove
real talk though: pmdaunbound is launched by pmcd(1) and should never be executed directly. like, don't. πŸ™ˆ

the Install and Remove scripts are the ones that notify pmcd(1) when the agent gets installed or removed, so they handle the whole announcement. very main character of them πŸ‘‘


🧚 FILES 🧚

  • $PCP_PMDAS_DIR/unbound/Install β€” the installation script for the pmdaunbound agent
  • $PCP_PMDAS_DIR/unbound/Remove β€” the undo installation script for the pmdaunbound agent
  • $PCP_LOG_DIR/pmcd/unbound.log β€” the default log file where error messages from pmdaunbound go πŸ“

πŸ’œ PCP ENVIRONMENT πŸ’œ

environment variables with the prefix PCP_ are what 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 the $PCP_CONF variable may be used to specify an alternative configuration file, as described in pcp.conf(5). iykyk πŸ’…


πŸ”₯ SEE ALSO πŸ”₯

PCPIntro(1), pmcd(1), unbound(8) and unbound-control(8).


that's the whole page bestie, go forth and monitor your resolver πŸ’–βœ¨

this was Performance Co-Pilot's PCP release of PMDAUNBOUND(1) β€” mwah, slay, bye πŸ«ΆπŸ‘‘

πŸ“¦ where this page comes from