Performance Co-Pilot | Iserver Admin
24/7 Customer Support
06Jun 2017




Performance Co-Pilot

Let us Read for you.

Performance Co-Pilot

It is also one of the open source toolkits. Performance-Copilot is best known for monitoring and management system level performance. It can be used for the most complex system configurations and performance related problems in a distributed and scalable service.

Perhaps, it has many different platforms like MacOSX, Free BSD, IRIX, Solaris, and Windows. It consists of two classes of software utility:#server management services


  • PCP Collectors– It collects and extracts performance data, for instance: kernel and database.
  • PCP Monitors– It is one of the parts of PCP that represent data from the hosts that have the PCP collector installed separately into it.
  • Moreover, there are also some monitoring tools such as the PM chart in layered packages that build on the core PCP functionality. There are also some monitoring applications that are mainly console based and run directly from the command line.


Pmstat – ASCII output and the high-level summary of system performance.

PMIE- it is an inference engine to perform alarms and automate system management tasks by evaluating predicate action rules.

PMINFO- it is a metadata that describes the interrogates specific performance metrics.

PMLOGGER– Most of the PCP tools generate PCP archives for their smooth replay.

PMVAL- It provides the information about the some or all the instances of performance metrics and time control.



/etc/pcp.conf- Configuration file for the PCP runtime environment, see pcp.conf (5).

$PCP_RC_DIR/pcp-  Script for starting and stopping pmcd (1).

$PCP_PMCDCONF_PATH-  Control file for pmcd (1).

$PCP_PMCDOPTIONS_PATH-  Command line options passed to pmcd (1) when it is started from $PCP_RC_DIR/pcp . All the command line option lines should start with a hyphen as the first character. This file can also contain environment variable settings of the form “VARIABLE=value”.

$PCP_BINADM_DIR-  Location of PCP utilities for collecting and maintaining PCP archives, PMDA help text, PMNS files etc.

$PCP_PMDAS_DIR-  Parent directory of the installation directory for Dynamic Shared Object (DSO) PMDAs.

$PCP_RUN_DIR/   If pmcd is running, this file contains an ascii decimal representation of its process ID.

$PCP_LOG_DIR/pmcd-  Default location of log files for pmcd (1), current directory for running PMDAs. Archives generated by pmlogger (1) are generally below $PCP_LOG_DIR/pmlogger .

$PCP_LOG_DIR/pmcd/pmcd.log-  Diagnostic and status log for the current running pmcd (1) process. The first place to look when there are problems associated with pmcd .

$PCP_LOG_DIR/pmcd/pmcd.log.prev-  Diagnostic and status log for the previous pmcd (1) instance.

$PCP_LOG_DIR/NOTICES-  Log of pmcd (1) and PMDA starts, stops, additions and removals.

$PCP_VAR_DIR/config-  Contains directories of configuration files for several PCP tools.

$PCP_VAR_DIR/config/pmcd/rc.local-  Local script for controlling PCP boot, shutdown and restart actions.

$PCP_VAR_DIR/pmns/root- The ASCII $PCP_LOG_DIR/NOTICES/pmns (5) exported by pmcd (1) by default. This PMNS is be the super set of all other PMNS files installed in $PCP_VAR_DIR/pmns .

$PCP_LOG_DIR/NOTICES-  In addition to the pmcd (1) and PMDA activity, may be used to log alarms and notices from pmie (1) via pmpost (1).

$PCP_VAR_DIR/config/pmlogger/control-  Control file for pmlogger (1) instances launched from $PCP_RC_DIR/pcp and/or managed by pmlogger_check (1) and pmlogger_daily (1) as part of a production PCP archive collection setup.


This document describes the high-level features and options common to most PCP utilities available on all platforms.

Comments (0)