This guide will assist new users by clearly showing how to solve specific problem scenarios that users encounter frequently. The aim of this guide is to assist first-time users to become more productive right away.
This guide contains the following topics:
List the available performance metrics, introduces the pminfo command to display various types of information about performance metrics available.
Add new metrics to the available set, covers adding mounts metrics to pmcd.
Record metrics on my local system, covers setup of logging to record metrics from local system.
Record metrics from a remote system, covers setup of logging from remote systems.
Graph a performance metric, introduces pmchart - a strip chart tool for Performance Co-Pilot.
Automate performance problem detection, introduces pmieconf which is used to display and modify variables or parameters controlling the details of the generated pmie rules.
Setup automated rules to write to the system log, uses pmieconf - a utility for viewing and configuring variables from generalized pmie (1) rules.
Record historical values for use with the pcp-dstat tool, introduces pcp-dstat tool which is a general performance analysis tool to view multiple system resources instantly.
Export metric values in a comma-separated format, introduces pmrep which is a customizable performance metrics reporting tool.
Using Charts, introduces the basic functionality available in the PCP Strip Chart tool - pmchart.
Managing Archive, covers PCP tools for creating and managing PCP archives.
Automated Reasoning with pmie covers the pmie tool within PCP that is designed for automated filtering and reasoning about performance.
Configuring Automated Reasoning, covers customization of pmie rules using pmieconf.
Analyzing Linux Containers, introduces how to extract performance data from individual containers using the PCP tools.
Establishing Secure Connections, covers setting up secure connections between PCP collector and monitor components. Also, how network connections can be made secure against eavesdropping, data tampering and man-in-the-middle class attacks.
Establishing Secure Client Connections, covers setting up secure connections between PCP collector and monitor components and discuss setting up certificates on both the collector and monitor hosts.
Setup Authenticated Connections, covers setting up authenticated connections between PCP collector and monitor components.
Importing data and creating PCP archives, describes an alternative method of importing performance data into PCP by creating PCP archives from files or data streams that have no knowledge of PCP.
Using 3D views, covers performance visualisation with pmview.
Compare Archives and Report Significant Differences, introduces the pmdiff tool that compares the average values for every metric in a given time window, for changes that are likely to be of interest when searching for performance regressions.
This guide is written for the system administrator or performance analyst who is directly using and administering PCP applications.
The operating system man pages provide concise reference information on the use of commands, subroutines, and system resources. There is usually a man page for each PCP command or subroutine. To see a list of all the PCP man pages, start from the following command:
Each man page usually has a “SEE ALSO” section, linking to other, related entries.
To see a particular man page, supply its name to the man command, for example:
The man pages are arranged in different sections - user commands, programming interfaces, and so on. For a complete list of manual sections on a platform enter the command:
When referring to man pages, this guide follows a standard convention: the section number in parentheses follows the item. For example, pminfo(1) refers to the man page in section 1 for the pminfo command.
The following web site is accessible to everyone:
URL : https://pcp.io
PCP is open source software released under the GNU General Public License (GPL) and GNU Lesser General Public License (LGPL)
The following conventions are used throughout this document:
A brace-enclosed all-capital-letters syntax indicates a variable that has been sourced from the global
This fixed-width font denotes literal items such as commands, files, routines, path names, signals, messages, and programming language structures.
Italic typeface denotes variable entries and words or concepts being defined.
This bold, fixed-space font denotes literal items that the user enters in interactive sessions. (Output is shown in nonbold, fixed-space font.)
Brackets enclose optional portions of a command or directive line.
Ellipses indicate that a preceding element can be repeated.
All capital letters denote environment variables, operator names, directives, defined constants, and macros in C programs.
Parentheses that follow function names surround function arguments or are empty if the function has no arguments; parentheses that follow commands surround man page section numbers.