PMLOGGER_MERGE(1)

💖 PMLOGGER_MERGE 💖

okay bestie, so pmlogger_merge — that's a General Commands Manual situation, manual page PMLOGGER_MERGE(1) — is literally a helper script that merges Performance Co-Pilot archives. sit down, we're doing this 🫶

---

✨ SYNOPSIS ✨

$PCP_BINADM_DIR/pmlogger_merge [-fNVE?]  [input-basename ... output-name]

that's it. that's the whole vibe. no cap.

---

🌸 DESCRIPTION 🌸

so pmlogger_merge is a helper script — a little guy with main character energy — and it's the one pmlogger_daily(1) calls in when it needs to merge all of the Performance Co-Pilot (PCP) archives for a single host on a single day into one combined PCP archive. one host, one day, one archive. it's giving organization 💅

under the hood it's a wrapper script for pmlogextract(1), and what it does is merge every archive matching the input-basename arguments and then create a brand new archive using output-name as the base name for the physical files that constitute an archive. iconic behaviour honestly.

oh and also — the input-basename arguments are allowed to contain meta characters, in the style of sh(1). glob away, queen 🎀

and here's a fun little detail: if any of the files that are components of the input-basename archives has been compressed, then on success pmlogger_merge will compress output-name using pmlogcompress(1). it matches the energy. if you brought compressed files, you're leaving with compressed files. periodt.

---

✨ OPTIONS ✨

The available command line options are — and bestie, yes, you need all of them:

• -f, --force — this option causes all of the input files to be removed once the output archive has been created. bye bye input files, you did great 🫡
• -N, --showme — runs pmlogger_merge in a show me'' / dry run'' mode where the tasks that would be performed get reported, but literally no changes are made. nothing happens. it's all talk, no action, and that's on purpose. this is typically used for debugging, in combination with one (verbose) or two (very verbose) -V options.
• -V, --verbose — increase verbosity in the output progress report. more -V = more talking. two of them and it will NOT stop yapping.
• -E, --expunge — okay so when metric metadata differences show up between the archives you're merging, the default behaviour is for pmlogger_merge to fail with a fatal error, and the output-name archive does not get created. 💀 the -E flag instead issues a warning and excludes the affected metrics from the merged output archive. this is intended for automated daily archive rotation, where it is highly desirable for unattended daily archive merging, rewriting and compression to succeed. see also pmlogger_daily(1) and the -x flag to pmlogextract(1).
• -?, --help — display usage message and exit. the classic. ask for help, receive help, leave. 🌈

---

🧚 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. and — plot twist — the $PCP_CONF variable may be used to specify an alternative configuration file, as described in pcp.conf(5). so if you ever need to point at a different config, that's your girl ✨

---

👑 SEE ALSO 👑

PCPIntro(1), pmlogcompress(1), pmlogextract(1), pmlogger(1) and pmlogger_daily(1).

go read them, they're all in the group chat 💜

---

that's the whole page bestie, you ate it up fr fr 🌸💅✨

mwah 💖 — brought to you by Performance Co-Pilot, version PCP, filed under PMLOGGER_MERGE(1). love that for us 🎀