mrtg2pcp(1) [centos man page]

MRTG2PCP(1)						       Performance Co-Pilot						       MRTG2PCP(1)

NAME

       mrtg2pcp - Import mrtg data and create a PCP archive

SYNOPSIS

       mrtg2pcp hostname devname timezone infile outfile

DESCRIPTION

       mrtg2pcp is intended to read an MRTG log file as created by mrtg(1) and translate this into a Performance Co-Pilot (PCP) archive with the
       basename outfile.  The hostname, devname, and timezone arguments specify information about the system for which the statistics were
       gathered.

       The resultant PCP achive may be used with all the PCP client tools to graph subsets of the data using pmchart(1), perform data reduction
       and reporting, filter with the PCP inference engine pmie(1), etc.

       A series of physical files will be created with the prefix outfile.  These are outfile.0 (the performance data), outfile.meta (the metadata
       that describes the performance data) and outfile.index (a temporal index to improve efficiency of replay operations for the archive).  If
       any of these files exists already, then mrtg2pcp will not overwrite them and will exit with an error message of the form

       __pmLogNewFile: "blah.0" already exists, not over-written

       mrtg2pcp is a Perl script that uses the PCP::LogImport Perl wrapper around the PCP libpcp_import library, and as such could be used as an
       example to develop new tools to import other types of performance data and create PCP archives.

SEE ALSO

       logimport(3), PCP::LogImport(3pm), pmchart(1), pmie(1) pmlogger(1).

3.8.10							       Performance Co-Pilot						       MRTG2PCP(1)

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)