What are the typical Performance Co-Pilot (PCP) deployment strategies?

PCP has a fully distributed architecture, which offers substantial flexibility in site deployment. The Performance Monitoring Collection Daemon (pmcd in the pcp base package) is deployed on the system(s) to be monitored, generally servers, and the client tools (base pcp package and the pcp-gui package) are generally deployed on user workstations (and servers if desired).

• The pmlogger(1) daemon may be considered a client tool for these purposes and can be used to capture performance logs of either a local system or a remote system, provided those systems are running the pmcd daemon.
• The normal and simplest configuration uses pmlogger to capture performance logs from the local system only.
• A deployment where pmlogger is configured to capture performance logs from one or more remote systems is termed a pmlogger "farm", and is similar in concept to a dedicated syslog server.
• in all configurations, there is one pmlogger(1) process capturing performance data from one host only, either local or remote. PCP performance data archive logs contain data for one host only.

The various PCP deployment options are fully described in the Content from www.pcp.io is not included.Performance Co-Pilot User's and Administrator's Guide, specifically in the chapter on Content from www.pcp.io is not included.PCP deployment options

See Also

• Index of Performance Co-Pilot (PCP) articles, solutions, tutorials and white papers
• Content from pcp.io is not included.PCP Quick Reference Guide
• Introduction to storage performance analysis with PCP
• Content from www.pcp.io is not included.Performance Co-Pilot User's and Administrator's Guide