pcp
[Top] [All Lists]

[PATCH] Linkify PCP Quick Guide

To: pcp@xxxxxxxxxxx
Subject: [PATCH] Linkify PCP Quick Guide
From: Marko Myllynen <myllynen@xxxxxxxxxx>
Date: Fri, 12 Sep 2014 16:06:41 +0300
Delivered-to: pcp@xxxxxxxxxxx
Organization: Red Hat
Reply-to: myllynen@xxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
>From b4054decc9eff82113f39c963eb16a57fcd6e70c Mon Sep 17 00:00:00 2001
From: Marko Myllynen <myllynen@xxxxxxxxxx>
Date: Fri, 12 Sep 2014 16:03:55 +0300
Subject: [PATCH] Linkify PCP Quick Guide

---
 man/html/guide.redhat.html |   84 ++++++++++++++++++++++----------------------
 1 files changed, 42 insertions(+), 42 deletions(-)

diff --git a/man/html/guide.redhat.html b/man/html/guide.redhat.html
index 1b09e58..e675a81 100644
--- a/man/html/guide.redhat.html
+++ b/man/html/guide.redhat.html
@@ -72,7 +72,7 @@
 </B></TD></TR>
 </TABLE>
 
-<P>This will enable the Performance Metrics Collector Daemon (pmcd) on the 
host which then in turn will control and request metrics on behalf of clients 
from various Performance Metrics Domain Agents (PMDAs). The PMDAs provide the 
actual data from different components (domains) in the system, for example from 
the Linux Kernel PMDA or the NFS Client PMDA. The default configuration 
includes over 1000 metrics with negligible overall overhead. Local PCP archive 
logs will also be enabled on the host for convenience with pmlogger (<A 
HREF="https://access.redhat.com/articles/1146283";>RHKB 1146283</A> contains 
some additional logging related considerations).
+<P>This will enable the Performance Metrics Collector Daemon (<a 
href="http://man7.org/linux/man-pages/man1/pmcd.1.html";>pmcd(1)</a>) on the 
host which then in turn will control and request metrics on behalf of clients 
from various Performance Metrics Domain Agents (PMDAs). The PMDAs provide the 
actual data from different components (domains) in the system, for example from 
the Linux Kernel PMDA or the NFS Client PMDA. The default configuration 
includes over 1000 metrics with negligible overall overhead. Local PCP archive 
logs will also be enabled on the host for convenience with <a 
href="http://man7.org/linux/man-pages/man1/pmlogger.1.html";>pmlogger(1)</a> (<A 
HREF="https://access.redhat.com/articles/1146283";>RHKB 1146283</A> contains 
some additional logging related considerations).
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
        <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;To 
enable PMDAs which are not enabled by default, for example the NFS Client PMDA, 
run the corresponding Install script:<br><B>
@@ -107,12 +107,12 @@
 
 <P>Checks for remote log collection will be done every half an hour. You may 
also wish to run /usr/libexec/pcp/bin/pmlogger_check -V -C manually (the 
service restart above issues this command internally).
 
-<P>Note that a default configuration file (config.acme.com above) will be 
generated if it does not exist already. This process is optional (a custom 
configuration for each host can be provided instead), see the pmlogconf manual 
page for details on this.
+<P>Note that a default configuration file (config.acme.com above) will be 
generated if it does not exist already. This process is optional (a custom 
configuration for each host can be provided instead), see the <a 
href="http://man7.org/linux/man-pages/man1/pmlogconf.1.html";>pmlogconf(1) 
manual page</a> for details on this.
 
 <a name="discovery"></a>
 <H3>Dynamic Host Discovery</H3>
 
-<P>In dynamic environments manually configuring every host is not feasible, 
perhaps even impossible. PCP Manager (PMMGR, from the pcp-manager RPM package) 
can be used instead of directly invoking PMLOGGER and PMIE to auto-discover and 
auto-configure new collector hosts.
+<P>In dynamic environments manually configuring every host is not feasible, 
perhaps even impossible. PCP Manager (<a 
href="http://man7.org/linux/man-pages/man1/pmmgr.1.html";>pmmgr(1)</a>, from the 
pcp-manager RPM package) can be used instead of directly invoking PMLOGGER and 
PMIE to auto-discover and auto-configure new collector hosts.
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
        <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;To 
install the PMMGR daemon and begin monitoring either statically or dynamically 
configured hosts, run:<br><B>
@@ -129,7 +129,7 @@
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Discover use of the PCP pmcd service on the local network:<BR><B>
-<BR> $ pmfind -s pmcd</B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pmfind.1.html";>pmfind</a> 
-s pmcd</B>
 </TD></TR>
 </TABLE>
 
@@ -140,7 +140,7 @@ Discover use of the PCP pmcd service on the local 
network:<BR><B>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;Check 
PCP services on remote host <B><FONT COLOR="#cc0000">munch</FONT></B> and 
historically, from a local archive for host <B><FONT 
COLOR="#cc0000">smash</FONT></B>:<BR><B>
-<BR> $ pcp -h <FONT COLOR="#cc0000">munch</FONT></B><PRE>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pcp.1.html";>pcp</a> -h 
<FONT COLOR="#cc0000">munch</FONT></B><PRE>
 Performance Co-Pilot configuration on munch:
   platform: SunOS munch 5.11 oi_151a8 i86pc
   hardware: 4 cpus, 3 disks, 4087MB RAM
@@ -149,7 +149,7 @@ Performance Co-Pilot configuration on munch:
       pmda: pmcd mmv solaris
 </PRE>
 <B>
-<BR> $ pcp -a /var/log/pcp/pmlogger/<FONT 
COLOR="#cc0000">smash</FONT>/20140729</B><PRE>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pcp.1.html";>pcp</a> -a 
/var/log/pcp/pmlogger/<FONT COLOR="#cc0000">smash</FONT>/20140729</B><PRE>
 Performance Co-Pilot configuration on smash:
   archive: /var/log/pcp/pmlogger/smash/20140729
  platform: Linux smash 2.6.32-279.46.1.el6.x86_64 #1 SMP Mon May 19 16:16:00 
EDT 2014 x86_64
@@ -174,56 +174,56 @@ Performance Co-Pilot configuration on smash:
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Display all the enabled performance metrics on a host (use with -t to include 
a short description for each):<BR><B>
-<BR> $ pminfo -h <FONT COLOR="#cc0000">acme.com</FONT></B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pminfo.1.html";>pminfo</a> 
-h <FONT COLOR="#cc0000">acme.com</FONT></B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Display detailed information about a performance metric and its current 
values:<BR><B>
-<BR> $ pminfo -dfmtT disk.partitions.read -h <FONT 
COLOR="#cc0000">acme.com</FONT></B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pminfo.1.html";>pminfo</a> 
-dfmtT disk.partitions.read -h <FONT COLOR="#cc0000">acme.com</FONT></B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Monitor live disk write operations per partition with two second interval 
using fixed point notation (use -i instance to list only certain metrics and -r 
for raw values):<BR><B>
-<BR> $ pmval -t 2sec -f 3 disk.partitions.write -h <FONT 
COLOR="#cc0000">acme.com</FONT></B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pmval.1.html";>pmval</a> 
-t 2sec -f 3 disk.partitions.write -h <FONT COLOR="#cc0000">acme.com</FONT></B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Monitor live CPU load, memory usage, and disk write operations per partition 
with two second interval using fixed width columns:<BR><B>
-<BR> $ pmdumptext -i -l 'kernel.all.load[1]' mem.util.used 
disk.partitions.write -h <FONT COLOR="#cc0000">acme.com</FONT></B>
+<BR> $ <a 
href="http://man7.org/linux/man-pages/man1/pmdumptext.1.html";>pmdumptext</a> -i 
-l 'kernel.all.load[1]' mem.util.used disk.partitions.write -h <FONT 
COLOR="#cc0000">acme.com</FONT></B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Monitor system metrics in a top like window (this needs a large 
terminal):<BR><B>
-<BR> $ pmatop -h <FONT COLOR="#cc0000">acme.com</FONT></B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pmatop.1.html";>pmatop</a> 
-h <FONT COLOR="#cc0000">acme.com</FONT></B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20> 
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Monitor system metrics in a sar like fashion with two second interval from two 
different hosts:<BR><B>
-<BR> $ pmstat -t 2sec -h <FONT COLOR="#cc0000">acme1.com</FONT> -h <FONT 
COLOR="#cc0000">acme2.com</FONT></B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pmstat.1.html";>pmstat</a> 
-t 2sec -h <FONT COLOR="#cc0000">acme1.com</FONT> -h <FONT 
COLOR="#cc0000">acme2.com</FONT></B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Monitor system metrics in an iostat like fashion with two second 
interval:<BR><B>
-<BR> $ pmiostat -t 2sec -h <FONT COLOR="#cc0000">acme.com</FONT></B>
+<BR> $ <a 
href="http://man7.org/linux/man-pages/man1/pmiostat.1.html";>pmiostat</a> -t 
2sec -h <FONT COLOR="#cc0000">acme.com</FONT></B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20> 
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Monitor performance metrics with a GUI application with two second default 
interval from two different hosts. Use File-&gt;New Chart to select metrics to 
be included in a new view and use File-&gt;Open View to use a predefined 
view:<BR><B>
-<BR> $ pmchart -t 2sec -h <FONT COLOR="#cc0000">acme1.com</FONT> -h <FONT 
COLOR="#cc0000">acme2.com</FONT></B>
+<BR> $ <a 
href="http://man7.org/linux/man-pages/man1/pmchart.1.html";>pmchart</a> -t 2sec 
-h <FONT COLOR="#cc0000">acme1.com</FONT> -h <FONT 
COLOR="#cc0000">acme2.com</FONT></B>
 </TD></TR>
 </TABLE>
 
@@ -235,112 +235,112 @@ Monitor performance metrics with a GUI application with 
two second default inter
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Check the host and the time period an archive covers:<BR><B>
-<BR> $ pmdumplog -l <FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
+<BR> $ <a 
href="http://man7.org/linux/man-pages/man1/pmdumplog.1.html";>pmdumplog</a> -l 
<FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Check PCP configuration at the time when an archive was created:<BR><B>
-<BR> $ pcp -a <FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pcp.1.html";>pcp</a> -a 
<FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Display all enabled performance metrics at the time when an archive was 
created:<BR><B>
-<BR> $ pminfo -a <FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pminfo.1.html";>pminfo</a> 
-a <FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Display detailed information about a performance metric at the time when an 
archive was created:<BR><B>
-<BR> $ pminfo -df mem.freemem -a <FONT 
COLOR="#cc0000">acme.com</FONT>/20140902</B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pminfo.1.html";>pminfo</a> 
-df mem.freemem -a <FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Dump past disk write operations per partition in an archive using fixed point 
notation (use -i instance to list only certain metrics and -r for raw 
values):<BR><B>
-<BR> $ pmval -f 3 disk.partitions.write -a <FONT 
COLOR="#cc0000">acme.com</FONT>/20140902</B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pmval.1.html";>pmval</a> 
-f 3 disk.partitions.write -a <FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Replay past disk write operations per partition in an archive with two second 
interval using fixed point notation between 9 AM and 10 AM (use full dates with 
syntax like @"2014-08-20 14:00:00"):<BR><B>
-<BR> $ pmval -d -t 2sec -f 3 disk.partitions.write -S @09:00 -T @10:00 -a 
<FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pmval.1.html";>pmval</a> 
-d -t 2sec -f 3 disk.partitions.write -S @09:00 -T @10:00 -a <FONT 
COLOR="#cc0000">acme.com</FONT>/20140902</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Calculate average values of performance metrics in an archive between 9 AM / 
10 AM using table like formatting including the time of minimum/maximum value 
and the actual minimum/maximum value:<BR><B>
-<BR> $ pmlogsummary -HlfiImM -S @09:00 -T @10:00 <FONT 
COLOR="#cc0000">acme.com</FONT>/20140902 disk.partitions.write mem.freemem</B>
+<BR> $ <a 
href="http://man7.org/linux/man-pages/man1/pmlogsummary.1.html";>pmlogsummary</a>
 -HlfiImM -S @09:00 -T @10:00 <FONT COLOR="#cc0000">acme.com</FONT>/20140902 
disk.partitions.write mem.freemem</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Dump past CPU load, memory usage, and disk write operations per partition in 
an archive averaged over 10 minute interval with fixed columns between 9 AM and 
10 AM:<BR><B>
-<BR> $ pmdumptext -t 10m -i -l -S @09:00 -T @10:00 'kernel.all.load[1]' 
'mem.util.used' 'disk.partitions.write' -a <FONT 
COLOR="#cc0000">acme.com</FONT>/20140902</B>
+<BR> $ <a 
href="http://man7.org/linux/man-pages/man1/pmdumptext.1.html";>pmdumptext</a> -t 
10m -i -l -S @09:00 -T @10:00 'kernel.all.load[1]' 'mem.util.used' 
'disk.partitions.write' -a <FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Summarize differences in past performance metrics between two archives, 
comparing 2 AM / 3 AM in the first archive to 9 AM / 10 AM in the second 
archive (grep for '+' to quickly see values which were zero during the first 
period):<BR><B>
-<BR> $ pmdiff -S @02:00 -T @03:00 -B @09:00 -E @10:00 <FONT 
COLOR="#cc0000">acme.com</FONT>/20140902 <FONT 
COLOR="#cc0000">acme.com</FONT>/20140901</B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pmdiff.1.html";>pmdiff</a> 
-S @02:00 -T @03:00 -B @09:00 -E @10:00 <FONT 
COLOR="#cc0000">acme.com</FONT>/20140902 <FONT 
COLOR="#cc0000">acme.com</FONT>/20140901</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Replay past system metrics in an archive in a top like window starting 9 AM 
(this needs a large window):<BR><B>
-<BR> $ pmatop -S @09:00 -a <FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pmatop.1.html";>pmatop</a> 
-S @09:00 -a <FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Dump past system metrics in a sar like fashion averaged over 10 minute 
interval in an archive between 9 AM and 10 AM:<BR><B>
-<BR> $ pmstat -t 10m -S @09:00 -T @10:00 -a <FONT 
COLOR="#cc0000">acme.com</FONT>/20140902</B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pmstat.1.html";>pmstat</a> 
-t 10m -S @09:00 -T @10:00 -a <FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
-Dump past system metrics in an iostat(1) like fashion averaged over one hour 
interval in an archive:<BR><B>
-<BR> $ pmiostat -t 1h -a <FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
+Dump past system metrics in an <a 
href="http://man7.org/linux/man-pages/man1/iostat.1.html";>iostat(1)</a> like 
fashion averaged over one hour interval in an archive:<BR><B>
+<BR> $ <a 
href="http://man7.org/linux/man-pages/man1/pmiostat.1.html";>pmiostat</a> -t 1h 
-a <FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
-Dump past system metrics in a free(1) like fashion at a specific historical 
time offset:<BR><B>
-<BR> $ pcp -a <FONT COLOR="#cc0000">acme.com</FONT>/20140902 -O @10:02 free</B>
+Dump past system metrics in a <a 
href="http://man7.org/linux/man-pages/man1/free.1.html";>free(1)</a> like 
fashion at a specific historical time offset:<BR><B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pcp.1.html";>pcp</a> -a 
<FONT COLOR="#cc0000">acme.com</FONT>/20140902 -O @10:02 free</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Replay performance metrics with a GUI application with two second default 
interval in an archive between 9 AM and 10 AM. Use File-&gt;New Chart to select 
metrics to be included in a new view and use File-&gt;Open View to use a 
predefined view:<BR><B>
-<BR> $ pmchart -t 2sec -S @09:00 -T @10:00 -a <FONT 
COLOR="#cc0000">acme.com</FONT>/20140902 -O @10:02 free</B>
+<BR> $ <a 
href="http://man7.org/linux/man-pages/man1/pmchart.1.html";>pmchart</a> -t 2sec 
-S @09:00 -T @10:00 -a <FONT COLOR="#cc0000">acme.com</FONT>/20140902 -O @10:02 
free</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Merge several archives as a new combined archive (see the manual page how to 
write configuration file to collect only certain metrics):<BR><B>
-<BR> $ pmlogextract &lt;archive1&gt; &lt;archive2&gt; &lt;newarchive&gt;</B>
+<BR> $ <a 
href="http://man7.org/linux/man-pages/man1/pmlogextract.1.html";>pmlogextract</a>
 &lt;archive1&gt; &lt;archive2&gt; &lt;newarchive&gt;</B>
 </TD></TR>
 </TABLE>
 
 <a name="visual"></a>
 <H3>Visualizing iostat and sar Data</H3>
 
-<P>iostat and sar data can be imported as PCP archives which then allows 
inspecting and visualizing the data with PCP tools. The iostat2pcp importer is 
in the pcp-import-iostat2pcp package and the sar2pcp importer is in the 
pcp-import-sar2pcp package.
+<P><a href="http://man7.org/linux/man-pages/man1/iostat.1.html";>iostat</a> and 
<a href="http://man7.org/linux/man-pages/man1/sar.1.html";>sar</a> data can be 
imported as PCP archives which then allows inspecting and visualizing the data 
with PCP tools. The iostat2pcp importer is in the pcp-import-iostat2pcp package 
and the sar2pcp importer is in the pcp-import-sar2pcp package.
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
@@ -371,42 +371,42 @@ Import sar data from an existing sar archive to a new PCP 
archive and visualize
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Display all the available process related metrics:<BR><B>
-<BR> $ pminfo proc</B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pminfo.1.html";>pminfo</a> 
proc</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Monitor the number of open file descriptors of the process 1234:<BR><B>
-<BR> $ pmval -t 2sec 'proc.fd.count[1234]'</B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pmval.1.html";>pmval</a> 
-t 2sec 'proc.fd.count[1234]'</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Monitor the CPU time, memory usage (RSS), and the number of threads of the 
process 1234 (-host local: is a workaround needed for the time being):<BR><B>
-<BR> $ pmdumptext -h local: -t 2sec 'proc.psinfo.utime[1234]' 
'proc.memory.rss[1234]' 'proc.psinfo.threads[1234]'</B>
+<BR> $ <a 
href="http://man7.org/linux/man-pages/man1/pmdumptext.1.html";>pmdumptext</a> -h 
local: -t 2sec 'proc.psinfo.utime[1234]' 'proc.memory.rss[1234]' 
'proc.psinfo.threads[1234]'</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Display all the available process related metrics in an archive:<BR><B>
-<BR> $ pminfo proc -a <FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pminfo.1.html";>pminfo</a> 
proc -a <FONT COLOR="#cc0000">acme.com</FONT>/20140902</B>
 </TD></TR>
 </TABLE>
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
         <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;
 Display the number of running processes on 2014-08-20 14:00:<BR><B>
-<BR> $ pmval -s 1 -S @"2014-08-20 14:00" proc.nprocs -a <FONT 
COLOR="#cc0000">acme.com</FONT>/20140820</B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pmval.1.html";>pmval</a> 
-s 1 -S @"2014-08-20 14:00" proc.nprocs -a <FONT 
COLOR="#cc0000">acme.com</FONT>/20140820</B>
 </TD></TR>
 </TABLE>
 
 <a name="instrument"></a>
 <H3>Application Instrumentation</H3>
 
-<P>Applications can be instrumented in the PCP world by using Memory Mapped 
Values (MMVs). pmdammv is a PMDA which exports application level performance 
metrics using memory mapped files. It offers an extremely low overhead 
instrumentation facility that is well-suited to long running, mission critical 
applications where it is desirable to have performance metrics and availability 
information permanently enabled.
+<P>Applications can be instrumented in the PCP world by using Memory Mapped 
Values (MMVs). <a 
href="http://man7.org/linux/man-pages/man1/pmdammv.1.html";>pmdammv</a> is a 
PMDA which exports application level performance metrics using memory mapped 
files. It offers an extremely low overhead instrumentation facility that is 
well-suited to long running, mission critical applications where it is 
desirable to have performance metrics and availability information permanently 
enabled.
 
 <P>Application to be instrumented with MMV need to be PCP MMV aware, APIs are 
available for several languages including C, C++, Perl, and Python. Java 
applications may use the separate <A 
HREF="https://code.google.com/p/parfait/";>Parfait</A> class library for 
enabling MMV.
 
@@ -417,7 +417,7 @@ Display the number of running processes on 2014-08-20 
14:00:<BR><B>
 <a name="pmie"></a>
 <H1>Performance Metrics Inference</H1>
 
-<P>Performance Metrics Inference Engine (PMIE) can evaluate rules and generate 
alarms, run scripts, or automate system management tasks based on live or past 
performance metrics.
+<P>Performance Metrics Inference Engine (<a 
href="http://man7.org/linux/man-pages/man1/pmie.1.html";>pmie(1)</a>) can 
evaluate rules and generate alarms, run scripts, or automate system management 
tasks based on live or past performance metrics.
 
 <TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=20>
        <TR><TD BGCOLOR="#e2e2e2" WIDTH=70%><BR><IMG 
SRC="images/stepfwd_on.png" WIDTH=16 HEIGHT=16 BORDER=0>&nbsp;&nbsp;&nbsp;To 
enable PMIE, just enable and start the service:<br><B>
@@ -451,8 +451,8 @@ This example shows a PMIE script, checks its syntax, runs 
it against an archive,
     bloated = (  mem.util.used > 5 Gbyte )
 
       -> print "%v memory used on %h!"</PRE>
-<BR> $ pmie -C pmie.ex
-<BR> $ pmie -t 1min -c pmie.ex -S @09:00 -T @10:00 -a <FONT 
COLOR="#cc0000">acme.com</FONT>/20140820</B>
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pmie.1.html";>pmie</a> -C 
pmie.ex
+<BR> $ <a href="http://man7.org/linux/man-pages/man1/pmie.1.html";>pmie</a> -t 
1min -c pmie.ex -S @09:00 -T @10:00 -a <FONT 
COLOR="#cc0000">acme.com</FONT>/20140820</B>
 </TD></TR>
 </TABLE>
 
@@ -473,7 +473,7 @@ This example shows a PMIE script, checks its syntax, runs 
it against an archive,
 <a name="pmwebd"></a>
 <H3>Performance Metrics Web Daemon</H3>
 
-<P>Performance Metrics Web Daemon (PMWEBD) is a front-end to both PMCD and PCP 
archives, providing a JSON interface suitable for use by web-based tools 
wishing to access performance data over HTTP. Custom applications can access 
all the available PCP information using this method, including possible data 
generated by custom PMDAs.
+<P>Performance Metrics Web Daemon (<a 
href="http://man7.org/linux/man-pages/man1/pmwebd.1.html";>pmwebd(1)</a>) is a 
front-end to both PMCD and PCP archives, providing a JSON interface suitable 
for use by web-based tools wishing to access performance data over HTTP. Custom 
applications can access all the available PCP information using this method, 
including possible data generated by custom PMDAs.
 
 <a name="browse"></a>
 <H3>Web Interface for Performance Metrics</H3>
-- 
1.7.1

-- 
Marko Myllynen

<Prev in Thread] Current Thread [Next in Thread>
  • [PATCH] Linkify PCP Quick Guide, Marko Myllynen <=