pmjson - Man Page

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

pmjson is used to manipulate JSON (JavaScript Object Notation) formatted text used in the Performance Co-Pilot (PCP toolkit). It can produce minimal and human readable output formats when it is supplied with valid JSON input.

The available command line options are:

-i infile, --in=infile

JSON formatted input infile - path to a file from which input should be read. If this option is omitted, then pmjson will read from the standard input stream.

-m,  --minimal

Produce JSON output with all superfluous whitespace removed from the resulting JSON string.

-o outfile, --out=outfile

Formatted output is written to the named outfile. If this option is omitted, then pmjson will write to the standard output stream.

-n,  --not-pretty

Produce JSON output in raw, monochromatic format (default if output is being sent to a file).

-p,  --pretty

Produce JSON output in a human-friendly format (default if output is on a terminal).

-q,  --quiet

Verify the input as valid JSON only, no output is produced.

-V,  --version

Display version number and exit.

-y,  --yaml

Produce YAML-like output, a human-readable format with less syntactic sugar than JSON.

-?,  --help

Display usage message and exit.

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

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

PMWEBAPI(3).