5 PCP Command Reference
This table provides information about PCP commands.
| Action | Command | Description | 
|---|---|---|
| Performance metrics reporting tool. | pmrep | Generates reports from data collected by the Performance Metrics
                                Collector Daemon ( | 
| Arbitrary performance metrics valude dumper. | pmval | Outputs the current or archived values for a specific performance
                                metric from the  | 
| Review detailed information about a specific performance metric. | pminfo | Outputs the current or archived values for a specific performance
                                metric from the  | 
| High level system performance overview. | pmstat | Outputs a one line system performance overview on a timed interval. By default, a new line is output every five seconds. | 
| Compared archived logs and reports differences. | pmdiff | Outputs the differences from two archived logs created by the
                                Performance Metrics Logger ( | 
| Output collected or live performance data as plain text. | pmdumptext | Generates an ASCII format plain text file containing information
                                collected by the  | 
| Output internal information for an existing log archive. | pmdumplog | Outputs metadata for archived data collected by the
                                     | 
| Run dstatcommands within PCP. | pcp dstat | Provides compatibility for legacy scripts and troubleshooting
                                procedures that rely on the deprecated  | 
Reviewing Live Performance Metrics in Real Time
Use the pmrep and pmval commands to review live
        performance metrics.
                  
                To monitor all the outgoing metrics from the
                eth0 network interface in real time, use the
                pmrep command:
            
                     
sudo pmrep -i eth0 -v network.interface.out
                To monitor live hard drive operations for each partition with a
                two second interval, use the pmval command:
            
                     
sudo pmval -t 2sec -f 3 disk.partitions.writeReviewing Recorded Performance Metrics
Use the pmdumptext, pmstat, and
            pmdiff  commands to review metrics collected by the
            pmlogger service.
                  
 All the archives that the pmlogger service generates are stored in the
            /var/log/pcp/pmlogger/hostname directory. Navigate
            to this directory to review the archived performance metrics. 
                  
 The pmstat command can provide system performance metrics in a format
                similar to that produced by the sar command. For example, to review
                performance metrics averaged over a 10 minute interval between 09:00 and 10:00 on a specific
                date: 
                     
sudo pmstat -t 10m -S @09:00 -T @10:00 -a 20250113.0.xz To compare the metrics between two time periods, use the pmdiff command.
                For example, to compare the metrics between 02:00 and 03:00 on one day to the metrics between
                09:00 and 10:00 on a different day: 
                     
sudo pmdiff -S @02:00 -T @03:00 -B @09:00 -E @10:00 20250114.0.xz 20250113.0.xzReviewing Details About Recorded Performance Metrics
Use the pminfo command to review detailed information about specific
        performance metrics.
                  
                To review detailed information about a specific metric, use the
                pminfo command. For example, to review
                details about free memory:
            
                     
sudo pminfo -df mem.freemem -a 20250113.0.xzValidating System Status When Performance Metrics Were Captured
Use the pmdumplog and pminfo commands to validate
        system status when performance metrics were captured.
                  
 To verify the host, timezone, and time period that an archive containing performance metrics
                contains, use the pmdumplog command: 
                     
sudo pmdumplog -L 20250113.0.xz
                To review a list of every enabled performance metric, use the
                pminfo command:
            
                     
sudo pminfo -a 20250113.0.xzRunning dstat With PCP
               
               Use the pcp dstat command to review performance metrics collected by
        PCP.
                  
The dstat utility that was provided in previous Oracle Linux releases is no longer being actively developed. Instead, Performance Co-Pilot (PCP) provides many of the same functions for diagnosing system performance problems.
To review the command options provided for the pcp dstat command, run
                the following command:
                     
pcp dstat -hUsage: pcp-dstat [-afv] [options...] [delay [count]]
Versatile tool for generating system resource statistics
            
Dstat options:
-c, --cpu             enable cpu stats
-C 0,3,total          include cpu0, cpu3 and total
-d, --disk            enable disk stats
-D total,sda          include sda and total
...By default, running the command without any other options displays statistics about CPU, disk, network, page, and system:
pcp dstatYou did not select any stats, using -cdngy by default.
----total-usage---- -dsk/total- -net/total- ---paging-- ---system--
usr sys idl wai stl| read  writ| recv  send|  in   out | int   csw 
0   0 100   0   0|   0     0 | 198B  719B|   0     0 | 156   254 
0   0 100   0   0|   0    12k|  66B  302B|   0     0 | 160   264 
0   0  99   0   0|   0     0 | 132B  384B|   0     0 | 136   219 
...As with the previous iteration of the tool, pcp dstat generates a
                    running list of metrics and statistics in real time. To stop the process, press the
                    Ctrl + C keys.
                     
You can use different options to narrow the information output from the pcp
                dstat command command. For example, to display the metrics for CPU 1 only, run
                the following command:
                     
pcp dstat -c -C 1,total-----cpu1-usage---------total-usage----
usr sys idl wai stl:usr sys idl wai stl
0   0 100   0   0:  0   0 100   0   0
1   0 100   0   0:  0   0  99   0   0
0   0 100   0   0:  0   0 100   0   0
...Similarly, to display only network statistics of a specific interface, such as ens3, and
                    including totals, you would run the following command:
                     
pcp dstat -n -N ens3,total--net/ens3---net/total-
recv  send: recv  send
66B  350B:  66B  350B
66B  190B:  66B  190B
66B  198B:  66B  198B
66B  198B:  66B  198B
...To store any statistics that are being gathered into a file for later review, include the
                -o
                        outputfile option in the command.
                     
For example, to collect network statistics and save the information in the
                    /tmp/netstat-log file, and use the -f option to
                    output full information, run the following command:
                     
pcp dstat -n -f -o /tmp/netstat-log--net/ens3-----net/lo--
recv  send: recv  send
66B  358B:   0     0 
66B  174B:   0     0 
66B  190B:   0     0 
341B  419B:   0     0 
66B  190B:   0     0 
66B  190B:   0     0 
66B  190B:   0     0The output is saved in plain-text format. To review the contents of the
                    /tmp/netstat-log file, run the following command:
                     
cat /tmp/netstat-log...
"Host:","hostname",,,,"User:","user"
"Cmdline:","pcp-dstat -n -f -o /tmp/netstat-log",,,,"Date:","date"
"net/ens3",,"net/lo",
"net/ens3:recv","net/ens3:send","net/lo:recv","net/lo:send"
65.934,357.641,0,0
66.000,173.999,0,0
66.000,190.001,0,0
340.992,418.991,0,0
66.001,190.004,0,0
66,190,0,0
66.000,189.999,0,0