PMLOGSIZE(1)

πŸ’– PMLOGSIZE(1) πŸ’–

okay bestie, gather round, because we're diving into pmlogsize from the General Commands Manual and honestly? it's giving archive detective energy πŸ”βœ¨


🌸 NAME 🌸

pmlogsize β€” report sizes for parts of PCP archive(s) 🫢


✨ SYNOPSIS ✨



pmlogsize [-drv?]  [-D debug] [-x threshold] archive [...]

πŸ’… DESCRIPTION πŸ’…

so pmlogsize prints info about the size of the index, metadata and data sections of a Performance Co-Pilot (PCP) archive. no cap. πŸ“Š

and like, who is this for? two whole groups, bestie:

  • it's meant to guide improvements in archive encoding format for PCP developers πŸ‘©β€πŸ’»
  • and it helps trim pmlogger(1) configuration files so you can yeet metrics that are bloating the PCP archives with low-value data in production environments πŸ—‘οΈβœ¨

the archive arguments can be any mixture of:

  • the names of the physical files of a PCP archive, or
  • the basename that is common to all the component physical files in a single archive

in that second case, archive gets replaced by a list of all the matching component file names. slay, convenient. πŸŽ€

⚠️ heads up bestie, the semantics is a little different to other PCP tools in that foo.meta means just the file foo.meta, not foo.index, foo.meta, foo.0, etc. not me being pedantic, that's just literally how it works πŸ’€

πŸ‘‘ OPTIONS πŸ‘‘

the available command line options are, in no particular order because they're all iconic:

  • -d, --detail β€” enable detailed reporting 🧐 this means space per instance domain in a metadata file and space per metric (for values) in a data file.
  • -r, --replication β€” display additional info about possible replicated values in the data file and replicated instances in the metadata file πŸ” this option implies -d, so you get the detail too, no extra charge.
  • -x threshold, --threshold=threshold β€” with -d (or -r), cut off the report after at least threshold percent of the associated space (metric values or instance domains) has been reported βœ‚οΈ the default behaviour is equivalent to threshold being set to 100.
  • -v, --verbose β€” enable verbose mode πŸ—£οΈ this option can be provided more than once for additional verbosity (go off, stack 'em).
  • -?, --help β€” display usage message and exit πŸ‘‹

πŸ› 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. iykyk.

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 πŸ“


🌈 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 πŸ¦‹

PCPIntro(1), pmlogcheck(1), pmlogdump(1) and pmlogger(1) πŸ’œ


and that's the whole vibe check, bestie πŸŽ€ this page came to you straight from Performance Co-Pilot, aka PCP β€” mwah, take care of her, she's doing her best πŸ’–βœ¨πŸ«Ά periodt.

πŸ“¦ where this page comes from