PMNSADD(1)

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

✨ PMNSADD(1) ✨ β€” or, the little pmnsadd page from the General Commands Manual πŸ’–

okay bestie, gather round, we're talking about pmnsadd β€” the command that adds new names to the Performance Co-Pilot PMNS πŸ¦‹ (that's the Performance Metrics Name Space, and yes the acronym is doing the most, iykyk).


🌸 NAME 🌸

pmnsadd β€” add new names to the Performance Co-Pilot PMNS πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

$PCP_BINADM_DIR/pmnsadd [-?]  [-n namespace] file

πŸ’– DESCRIPTION πŸ’–

so first things first, and I need you to hear me on this one: pmnsmerge(1) performs the same function as pmnsadd and is faster, more robust and more flexible. so like… it is therefore recommended that pmnsmerge(1) be used instead. periodt. πŸ‘‘

but anyway, pmnsadd adds subtree(s) of new names into a Performance Metrics Name Space (PMNS), as used by the components of the Performance Co-Pilot (PCP). it's giving "new names, who dis" ✨

normally pmnsadd operates on the default Performance Metrics Name Space (PMNS), however if the -n option is specified an alternative namespace is used from the file namespace. slay, options.

the default PMNS is found in the file $PCP_VAR_DIR/pmns/root unless the environment variable PMNS_DEFAULT is set, in which case the value is assumed to be the pathname to the file containing the default PMNS. no cap. 🫢

the new names are specified in the file, arguments and conform to the syntax for PMNS specifications, see PMNS(5). and here's the vibe: there is one PMNS subtree in each file, and the base PMNS pathname to the inserted subtree is identified by the first group named in each file. e.g. if the specifications begin

myagent.foo.stuff {
    mumble    123:45:1
    fumble    123:45:2
}

then the new names will be added into the PMNS at the non-leaf position identified by myagent.foo.stuff, and following all other names with the prefix myagent.foo. literally iconic behaviour. 🌈

the new names must be contained within a single subtree of the namespace. if disjoint subtrees need to be added, these must be packaged into separate files and pmnsadd used on each, one at a time. one at a time, bestie, I'm so serious 🫠

all of the files defining the PMNS must be located within the directory that contains the root of the PMNS, this would typically be $PCP_VAR_DIR/pmns for the default PMNS, and this would typically imply running pmnsadd as root. yeah… root things. main character energy but with privileges. πŸ‘‘

as a special case, if file contains a line that begins root { then it is assumed to be a complete PMNS that needs to be merged, so none of the subtree extraction and rewriting is performed and file is handed directly to pmnsmerge(1). plot twist!! 🎭

provided some initial integrity checks are satisfied, pmnsadd will update the PMNS using pmnsmerge(1) β€” if this fails for any reason, the original namespace remains unchanged. she said "all or nothing" πŸ’…βœ¨


🧚 OPTIONS 🧚

the available command line options are:

  • -n pmnsfile β€” Load an alternative Performance Metrics Name Space (PMNS(5)) from the file pmnsfile. πŸ¦‹
  • -? β€” Display usage message and exit. (the classic "help me" coded move πŸ’€)

πŸ’€ CAVEATS πŸ’€

once the writing of the new namespace file has begun, the signals SIGINT, SIGHUP and SIGTERM will be ignored to protect the integrity of the new files. like, she is not taking calls right now, do not interrupt her while she's writing πŸš«πŸ“΅


πŸ“ FILES πŸ“

  • $PCP_VAR_DIR/pmns/root β€” the default PMNS, when the environment variable PMNS_DEFAULT is unset. 🌸

πŸ’œ 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. the $PCP_CONF variable may be used to specify an alternative configuration file, as described in pcp.conf(5). 🫢


🌈 SEE ALSO 🌈

pmnsdel(1), pmnsmerge(1), pcp.conf(5), pcp.env(5) and PMNS(5).


and that's the whole page, bestie!! πŸŽ€ this was Performance Co-Pilot β€” PCP β€” page PMNSADD(1), and it says bye from the bottom of the page. go use pmnsmerge(1) though, fr fr πŸ’–βœ¨

πŸ“¦ where this page comes from