PMDERIVEDERRSTR(3)

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

πŸ’… PMDERIVEDERRSTR(3) β€” pmDerivedErrStr πŸ’…

okay bestie, listen up β€” this is the Library Functions Manual page for pmDerivedErrStr, and honestly? She's tiny but she's mighty. πŸŽ€


✨ NAME ✨

pmDerivedErrStr β€” return error message from failure to parse derived metric definition 🫢


🌸 C SYNOPSIS 🌸

#include <pcp/pmapi.h>

char *pmDerivedErrStr(void);

cc ... -lpcp

yes she takes no args, yes she returns a char *, no we are not overthinking it πŸ’œ


πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the vibe. When you call pmRegisterDerived(3) to add a new derived metric definition, and something goes wrong β€” like, an error happens, bestie, it's giving chaos 😭 β€” you can then call pmDerivedErrStr to get the associated error message back. That's the whole job. She's the receipts. 🧾✨

like, pmRegisterDerived throws the party and things go sideways, and pmDerivedErrStr is the one who tells you what went sideways.

Also, lowkey important: the pmRegisterDerivedMetric interface is a convenience wrapper around both pmRegisterDerived and pmDerivedErrStr. So if you're feeling lazy (valid, no judgment πŸ™ˆ), that one does the two-step for you. Iconic behaviour honestly. πŸ‘‘


🌈 SEE ALSO 🌈


and that's the whole page, bestie β€” short, sweet, and she ate πŸ’…βœ¨ This one comes to you from Performance Co-Pilot, living under the name PMDERIVEDERRSTR(3). No date on the footer, so don't come for me, I'm just telling you what she said. πŸŽ€πŸ«ΆπŸ’–

πŸ“¦ where this page comes from