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

PMGETCONTEXTHOSTNAME(3) 				     Library Functions Manual					   PMGETCONTEXTHOSTNAME(3)

NAME

       pmGetContextHostName - return the hostname associated with a Performance Co-Pilot context

C SYNOPSIS

       #include <pcp/pmapi.h>

       const char *pmGetContextHostName(int id);

       cc ... -lpcp

DESCRIPTION

       Given  a valid PCP context identifier previously created with pmNewContext(3) or pmDupContext(3), the pmGetContextHostName function returns
       the hostname associated with id.

       If the context id is associated with an archive source  of  data,  the  hostname  returned  is  extracted  from	the  archive  label  using
       pmGetArchiveLabel(3).

       For  live  contexts,  an  attempt  will	first  be  made  to  retrieve the hostname from the PCP collector system using pmFetch(3) with the
       pmcd.hostname metric.  This allows client tools using this interface to retrieve an accurate host identifier even in the presence  of  port
       forwarding and tunnelled connections.

       Should  this not succeed, then a fallback method is used.  For local contexts - with local meaning any of DSO, ``localhost'' or Unix domain
       socket connection - a hostname will be sought via gethostname(3).  For other contexts, the hostname extracted from the initial context host
       specification will be used.

RETURN VALUE

       If id is not a valid PCP context identifier, this function returns a zero length string and hence never fails.

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).	Values for these variables may be obtained programmatically using the pmGetConfig(3) function.

SEE ALSO

       PCPIntro(1), PMAPI(3), gethostname(3), pmDupContext(3), pmFetch(3), pmGetArchiveLabel(3), pmNewContext(3), pcp.conf(5) and pcp.env(5).

Performance Co-Pilot							PCP						   PMGETCONTEXTHOSTNAME(3)

Linux and UNIX Man Pages

pcp(1) [centos man page]

Check Out this Related Man Page