PMJSON(1)

💖 PMJSON(1) — the Performance Co-Pilot JSON dumping utility, bestie edition 💖

okay so. this is pmjson, from the General Commands Manual section of the PCP docs. it's a whole vibe. let's go 🦋

---

✨ NAME ✨

pmjson — Performance Co-Pilot JSON dumping utility

---

🎀 SYNOPSIS 🎀

pmjson [-mnpqyV?]  [-D debug] [-i infile] [-o outfile]

---

🌸 DESCRIPTION 🌸

so pmjson is your girl for manipulating JSON (JavaScript Object Notation) formatted text, the kind used all over the Performance Co-Pilot (PCP) toolkit. 🫶

feed her some valid JSON input and she'll hand you back output — either the minimal kind or the human readable kind. your choice, bestie. 💅

---

👑 OPTIONS 👑

the available command line options are:

• -i infile, --in=infile — JSON formatted input infile: the path to a file you want the input read from. if you skip this option entirely, pmjson will read from the standard input stream instead. no file? no problem. 🎀
• -m, --minimal — produce JSON output with all the superfluous whitespace removed from the resulting JSON string. stripped. naked. clean. ✨
• -o outfile, --out=outfile — the formatted output gets written to the named outfile. omit it and pmjson writes to the standard output stream. easy. 🦋
• -n, --not-pretty — produce JSON output in raw, monochromatic format. this is the default if output is being sent to a file. it's giving plain but make it on purpose. 💀
• -p, --pretty — produce JSON output in a human-friendly format. this is the default if output is on a terminal. main character formatting, honestly. 👑
• -q, --quiet — verify the input as valid JSON only, no output is produced. just a vibe check on your JSON. did it pass? that's between you and your exit code. 🙈
• -V, --version — display version number and exit. iconic. ⭐
• -y, --yaml — produce YAML-like output, a human-readable format with less syntactic sugar than JSON. yes queen, less sugar but still sweet. 🍓
• -?, --help — display usage message and exit. when in doubt, ask her. 🧚

---

🌈 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).

---

🔥 DEBUGGING OPTIONS 🔥

the -D or --debug option enables the output of additional diagnostics on stderr to help triage problems — although ngl, the information is sometimes cryptic and primarily intended to provide guidance for developers rather than for end-users. 😭

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.

---

💜 SEE ALSO 💜

PMWEBAPI(3), pcp.conf(5) and pcp.env(5).

---

and that's the whole page, bestie!! 💖 this one came out of the Performance Co-Pilot crew over at PCP, and it's dated right there in the footer with the rest of the PMJSON(1) energy. go forth and format your JSON. periodt. 💅✨🎀