pcp(1) [centos man page]
PCP(1) General Commands Manual PCP(1) NAME
pcp - summarize a Performance Co-Pilot (PCP) installation SYNOPSIS
pcp [-p] [-a archive] [-h host] [-n pmnsfile] DESCRIPTION
The pcp command summarizes the status of a Performance Co-Pilot (PCP) installation. The report includes: the OS version, a summary of the hardware inventory, the local timezone, details of valid PCP licenses, the PCP software version, the state of the pmcd(1) process and asso- ciated Performance Metrics Domain Agents (PMDAs), as well as information about any PCP archive loggers (pmlogger(1)) and PCP inference engines (pmie(1)) that are running. For more general information about PCP, refer to PCPIntro(1). With no arguments, pcp reports on the local host, however the following options are accepted: -a archive Report the PCP configuration as described in the PCP archive log archive. -h host Report the PCP configuration on host rather than the local host. -n pmnsfile Load an alternative Performance Metrics Name Space (pmns(5)) from the file pmnsfile. -p Display pmie performance information - counts of rules evaluating to true, false, or indeterminate, as well as the expected rate of rule calculation, for each pmie process running on the default host. Refer to the individual metric help text for full details on these values. All of the displayed values are performance metric values and further information for each can be obtained using the command: $ pminfo -dtT metric The complete set of metrics required by pcp to produce its output is contained in $PCP_SYSCONF_DIR/pmlogger/config.pcp. When displaying running pmlogger instances, as a space-saving measure pcp will display a relative path to the archive being created if that archive is located below a pcplog subdirectory, otherwise the full pathname is displayed (the PCP log rotation and periodic pmlogger check- ing facilities support the creation of archives below $PCP_LOG_DIR/pmlogger/<hostname>). A similar convention is used for trimming the amount of information displayed for running pmie instances, where configuration files below $PCP_VAR_DIR/config will be displayed in truncated form. FILES
$PCP_SYSCONF_DIR/pmlogger/config.pcp pmlogger configuration file for collecting all of the metrics required by pcp. 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 configura- tion file, as described in pcp.conf(5). SEE ALSO
PCPIntro(1), pmcd(1), pmie(1), pmlogger(1), pcp.conf(5) and pcp.env(5). DIAGNOSTICS
pcp will terminate with an exit status of 1 if pmcd on the target host could not be reached or the archive could not be opened, or 2 for any other error. Performance Co-Pilot PCP PCP(1)
Check Out this Related Man Page
PMLOGCHECK(1) General Commands Manual PMLOGCHECK(1) NAME
pmlogcheck - checks for invalid data in a PCP archive SYNOPSIS
pmlogcheck [-lz] [-n pmnsfile] [-S start] [-T finish] [-Z timezone] archive DESCRIPTION
pmlogcheck prints information about the nature of any invalid data which it detects in a PCP archive. Of particular interest are wrapped values for metrics which are expected to have monotonically increasing values. The archive has the base name archive and must have been previously created using pmlogger(1). Normally pmlogcheck operates on the default Performance Metrics Namespace (pmns(5)), however if the -n option is specified an alternative namespace is loaded from the file pmnsfile. The command line options -S and -T can be used to specify a time window over which metrics should be summarized. These options are common to many Performance Co-Pilot tools and are fully described in PCPIntro(1). The -l option prints the archive label, showing the log format version, the time and date for the start and (current) end of the archive, and the host from which the performance metrics values were collected. By default, pmlogcheck reports the time of day according to the local timezone on the system where pmlogcheck is run. The -Z option changes the timezone to timezone in the format of the environment variable TZ as described in environ(5). The -z option changes the time- zone to the local timezone at the host that is the source of the performance metrics, as specified in the label record of the archive log. OUTPUT FORMAT
For each metric having ``counter'' semantics (i.e. the metric is expected to increase monotonically) which has been detected as having wrapped at some point in the archive, pmlogcheck produces output describing the metric name (with instance identifiers where appropriate), the internal storage type for the metric, the value of the metric before the counter wrap (with its associated timestamp), and the value of the metric after the wrap (also with a timestamp). pmlogcheck produces two different timestamp formats, depending on the interval over which it is run. For an interval greater than 24 hours, the date is displayed in addition to the time at which the counter wrap occurred. If the extent of the data being checked is less than 24 hours, a more precise format is used (time is displayed with millisecond precision, but without the date). FILES
$PCP_VAR_DIR/pmns/* default PMNS specification files $PCP_LOG_DIR/pmlogger/hostname default directory for PCP archives containing performance data collected from the host hostname. 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 configura- tion file, as described in pcp.conf(5). SEE ALSO
PCPIntro(1), pmdumplog(1), pmlogextract(1), pmlogger(1), pmlogmerge(1), pmlogsummary(1), pmval(1), pcp.conf(5), pcp.env(5) and pmns(5). DIAGNOSTICS
All are generated on standard error and are intended to be self- explanatory. Performance Co-Pilot PCP PMLOGCHECK(1)