PMREPCONF(1)

💖 PMREPCONF — bestie edition 💖

okay so you're reading the manual page for pmrepconf, from section 1 of the General Commands Manual, and honestly? it's giving "let me make you a config file and hold your hand the whole time" ✨

---

🎀 NAME 🎀

pmrepconf — create/edit a pmrep configuration file. that's it. that's the whole job. she makes them, she edits them, she slays 💅

---

🌸 SYNOPSIS 🌸

pmrepconf [-crvV?] [-D debug] [-d groupsdir] [-g grouptag] [-o option]
[-h host] configfile

like yes it looks like alphabet soup but every single letter is doing something i promise 🫶

---

✨ DESCRIPTION ✨

so pmrepconf is the girl who can create AND modify a generic configuration file for pmrep(1) and its related utilities, and she writes it all out in the pmrep.conf(5) format. periodt.

If configfile does not exist, she's gonna create a brand new generic configuration file for you, packed with a set of discovered metrics, all tucked into a [metrics] section. a whole little gift basket of metrics, no cap 🧺

Once it's created, that configfile can be used with the -c option to pmrep(1) and related utilities such as pcp2elasticsearch(2) and pcp2spark(2). besties sharing files, iconic.

If configfile does exist, she doesn't just barge in — she prompts you for input so you can enable or disable groups of related performance metrics. very considerate of her honestly 🥺

Group selection needs a simple y (yes) or n (no) response to the prompt Log this group?

and listen, at that same prompt you can also throw in other responses to trigger extra control functions, like:

• m — Report the names of the metrics in the current group. (get the receipts 📋)
• q — Finish with group selection (quit) and make no further changes to this group or any subsequent group. (she's done, bye ✋)
• /pattern — Make no change to this group but search for a group containing pattern in the description of the group or the names of the associated metrics. (ctrl+F but make it fashion 🔍)

When she's being run from automated setup processes, you use the -c option to indicate that pmrepconf is in auto-create mode and no interactive dialog takes place at all. The output configfile gets an extra comment message and a timestamp noting this fact, so it can be identified and subsequently updated using -c again. lowkey a little breadcrumb trail 🍞

⚠️ This option is not appropriate for interactive use of the tool. don't do it. she said what she said.

More verbose output may be enabled with the -v option, if you're nosy (affectionate).

---

🦋 SETUP GROUP FILES 🦋

When an initial configfile is created, the default specifications come from a set of group files sitting below the groupsdir specified with the -d option. And btw the default groupsdir is $PCP_VAR_DIR/config/pmlogconf, which is most commonly correct, so the -d option is rarely used in practice. it's the "i've never changed my ringtone" of directories 🌈

The directory structure and format of files below groupsdir is shared with the pmlogconf(1) utility, and described in detail on that manual page. go read hers, she's got the full lore. 📖

When used by pmrepconf all interval settings are ignored. not her business, not her problem 💅

---

💜 OPTIONS 💜

The available command line options are:

• -c — Enable non-interactive, auto-create mode. (set it and forget it ✨)
• -d groupsdir, --groups=groupsdir — Specify the path to the groupsdir directory.
• -g grouptag, --group=grouptag — Query logging state for the specific group named grouptag.
• -h host, --host=host — Performance metrics source is pmcd(1) on host, rather than on the default localhost. traveling for metrics ✈️
• -o option, --option=option — Specify an option to be added to the [option] section of the generated pmrep.conf(5) file. This command line option can be presented multiple times in order to added multiple lines in the [option] section. (yes, stack 'em up, she can handle it 🫶)
• -r, --reprobe — Reconsider every group for inclusion in the configfile. second chances, we love to see it 🔁
• -v, --verbose — Enable verbose mode. (tell me everything bestie 🗣️)
• -V, --version — Display version number and exit.
• -?, --help — Display usage message and exit.

---

🌟 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). the whole system runs on vibes and env vars tbh 🌈

pmrepconf overrides any $PCP_DERIVED_CONFIG environment variable to an empty string, for performance reasons. yeah she just does that. performance queen 👑

pmrepconf honours the $PMCD_WAIT_TIMEOUT environment variable when probing and creating new pmrep configuration files. She uses a default timeout value of 10 seconds for this, in the absence of an environment setting. ten seconds, that's the whole patience budget ⏳

---

🔥 DEBUGGING OPTIONS 🔥

The -D or --debug option enables the output of additional diagnostics on stderr to help triage problems, although the information is sometimes cryptic and primarily intended to provide guidance for developers rather than for end-users. ngl it's giving "the prophecy but in hex" 💀

debug is a comma separated list of debugging options; use pmdbg(1) with the -l option to obtain a list of the available debugging options and their meaning. go get the cheat sheet bestie 📜

---

👑 SEE ALSO 👑

pcp2elasticsearch(1), pcp2spark(1), pmcd(1), pmlogconf(1), pmrep(1), pcp.conf(5), pcp.env(5) and pmrep.conf(5)

---

and that's the whole page bestie!! this one came from Performance Co-Pilot / PCP, manual page PMREPCONF(1), and it's giving main character energy from start to finish 💖✨ go make some config files, you're gonna eat 🍓🧚‍♀️