1PCP-ATOPSAR(1) General Commands Manual PCP-ATOPSAR(1)
2
6 pcp-atopsar - Advanced System Activity Report (pcp-atop related)
7
9 pcp [pcp options] atopsar [atop options] [-r file|date] [-h host] [-R
10 cnt] [-b yy-mm-dd] hh:mm] [-e yy-mm-dd] hh:mm]
11 pcp [pcp options] atopsar [atop options] interval [samples]
12
14 The pcp-atopsar program can be used to report statistics at the system
15 level.
16 In the first synopsis line (no sampling interval specified), pcp-atop‐
18 sar extracts data from a raw logfile that has been recorded previously
19 by pmlogger(1) (or via the -w option of the pcp-atop program).
20 You can specify the name of the logfile with the -r option of the pcp-
21 atopsar program. When a pmlogger daily logfile is used, named
22 $PCP_LOG_DIR/pmlogger/[host]/YYYYMMDD (where YYYYMMDD reflects the
23 date), the required date of the form YYYYMMDD can be specified with the
24 -r option instead of the filename, or the symbolic name 'y' can be used
25 for yesterday's daily logfile (this can be repeated so 'yyyy' indicates
26 the logfile of four days ago). If the -r option is not specified at
27 all, today's daily logfile is used by default.
28 By default, the hostname of the localhost will be used when resolving
29 pmlogger archives, however an alternative host can be specified using
30 the -h option.
31 The starting and ending times of the report can be defined using the
32 options -b and -e followed by a time argument of the form [yy-mm-dd]
33 hh:mm.
34 In the second synopsis line, pcp-atopsar reads actual activity counters
36 from the kernel with the specified interval (in seconds) and the speci‐
37 fied number of samples (optionally). When pcp-atopsar is activated in
38 this way it immediately sends the output for every requested report to
39 standard output. If only one type of report is requested, the header
40 is printed once and after every interval seconds the statistical coun‐
41 ters are shown for that period. If several reports are requested, a
42 header is printed per sample followed by the statistical counters for
43 that period.
44 When invoked via the pcp(1) command, the PCPIntro(1) options -h/--host,
46 -a/--archive, -O/--origin, -s/--samples, -t/--interval, -Z/--timezone
47 and several other pcp options become indirectly available, see PCPIn‐
48 tro(1) for their descriptions.
49 Some generic flags can be specified to influence the behaviour of the
51 pcp-atopsar program:
52 -S By default the timestamp at the beginning of a line is suppressed
54 if more lines are shown for one interval. With this flag a time‐
55 stamp is given for every output-line (easier for post-processing).
56 -a By default certain resources as disks and network interfaces are
58 only shown when they were active during the interval. With this
59 flag all resources of a given type are shown, even if they were
60 inactive during the interval.
61 -x By default pcp-atopsar only uses colors if output is directed to a
63 terminal (window). These colors might indicate that a critical
64 occupation percentage has been reached (red) or has been almost
65 reached (cyan) for a particular resource. See the man-page of
66 atop for a detailed description of this feature (section COLORS).
67 With the flag -x the use of colors is suppressed unconditionally.
68 -C By default pcp-atopsar only uses colors if output is directed to a
70 terminal (window). These colors might indicate that a critical
71 occupation percentage has been reached (red) or has been almost
72 reached (cyan) for a particular resource. See the man-page of
73 atop for a detailed description of this feature (section COLORS).
74 With the flag -C colors will always be used, even if output is not
75 directed to a terminal.
76 -M Use markers at the end of a line to indicate that a critical occu‐
78 pation percentage has been reached ('*') or has been almost
79 reached ('+') for particular resources. The marker '*' is similar
80 to the color red and the marker '+' to the color cyan. See the
81 man-page of atop for a detailed description of these colors (sec‐
82 tion COLORS).
83 -H Repeat the header line within a report for every N detail lines.
85 The value of N is determined dynamically in case of output to a
86 tty/window (depending on the number of lines); for output to a
87 file or pipe this value is 23.
88 -R Summarize cnt samples into one sample. When the logfile contains
90 e.g. samples of 10 minutes, the use of the flag '-R 6' shows a re‐
91 port with one sample for every hour.
92 Other flags are used to define which reports are required:
94 -A Show all possible reports.
96 -c Report about CPU utilization (in total and per cpu).
98 -g Report about GPU utilization (per GPU).
100 -p Report about processor-related matters, like load-averages and
102 hardware interrupts.
103 -P Report about processes.
105 -m Current memory- and swap-occupation.
107 -s Report about paging- and swapping-activity, and overcommitment.
109 -B Report about Pressure Stall Information (PSI).
111 -l Report about utilization of logical volumes.
113 -f Report about utilization of multiple devices.
115 -d Report about utilization of disks.
117 -n Report about NFS mounted filesystems on NFS client.
119 -j Report about NFS client activity.
121 -J Report about NFS server activity.
123 -i Report about the network interfaces.
125 -I Report about errors for network-interfaces.
127 -w Report about IP version 4 network traffic.
129 -W Report about errors for IP version 4 traffic.
131 -y General report about ICMP version 4 layer activity.
133 -Y Per-type report about ICMP version 4 layer activity.
135 -u Report about UDP version 4 network traffic.
137 -z Report about IP version 6 network traffic.
139 -Z Report about errors for IP version 6 traffic.
141 -k General report about ICMP version 6 layer activity.
143 -K Per-type report about ICMP version 6 layer activity.
145 -U Report about UDP version 6 network traffic.
147 -t Report about TCP network traffic.
149 -T Report about errors for TCP-traffic.
151 -h Report about Infiniband utilization.
153 -O Report about top-3 processes consuming most processor capacity.
155 This report is only available when using a log file (not when
156 specifying an interval).
157 -G Report about top-3 processes consuming most resident memory. This
159 report is only available when using a log file (not when specify‐
160 ing an interval).
161 -D Report about top-3 processes issuing most disk transfers. This
163 report is only available when using a log file (not when specify‐
164 ing an interval).
165 -N Report about top-3 processes issuing most IPv4/IPv6 socket trans‐
167 fers. This report is only available when using a log file (not
168 when specifying an interval).
169
171 The following additional PCP command line long options are also avail‐
172 able:
173 --align=align
175 Force the initial sample to be aligned on the boundary of a natu‐
176 ral time unit align. Refer to PCPIntro(1) for a complete descrip‐
177 tion of the syntax for align.
178 --archive=archive
180 Performance metric values are retrieved from the set of Perfor‐
181 mance Co-Pilot (PCP) archive files identified by the argument ar‐
182 chive, which is a comma-separated list of names, each of which may
183 be the base name of an archive or the name of a directory contain‐
184 ing one or more archives.
185 --finish=endtime
187 When reporting archived metrics, the report will be restricted to
188 those records logged before or at endtime. Refer to PCPIntro(1)
189 for a complete description of the syntax for endtime.
190 --host=host
192 Fetch performance metrics from pmcd(1) on host, rather than from
193 the default localhost.
194 --hostzone
196 Use the local timezone of the host that is the source of the per‐
197 formance metrics, as identified by either the --host or the --ar‐
198 chive options. The default is to use the timezone of the local
199 host.
200 --hotproc
202 Use the pmdaproc(1) hotproc metrics.
203 --interval=interval
205 Set the reporting interval to something other than the default 1
206 second. The interval argument follows the syntax described in
207 PCPIntro(1), and in the simplest form may be an unsigned integer
208 (the implied units in this case are seconds).
209 --samples=samples
211 The samples option defines the number of samples to be retrieved
212 and reported.
213 --start=starttime
215 When reporting archived metrics, the report will be restricted to
216 those records logged at or after starttime. Refer to PCPIntro(1)
217 for a complete description of the syntax for starttime.
218 --timezone=timezone
220 Use timezone for the date and time. Timezone is in the format of
221 the environment variable TZ as described in environ(7).
222 --version
224 Display version number and exit.
225
227 Depending on the requested report, a number of columns with output val‐
228 ues are produced. The values are mostly presented as a number of
229 events per second.
230 The output for the flag -c contains the following columns per cpu:
232 usr% Percentage of cpu-time consumed in user mode (program text)
234 for all active processes running with a nice value of zero
235 (default) or a negative nice value (which means a higher
236 priority than usual). The cpu consumption in user mode of
237 processes with a nice value larger than zero (lower prior‐
238 ity) is indicated in the nice%-column.
239 nice% Percentage of cpu time consumed in user mode (i.e. program
241 text) for all processes running witn a nice value larger
242 than zero (which means with a lower priority than average).
243 sys% Percentage of cpu time consumed in system mode (kernel
245 text) for all active processes. A high percentage usually
246 indicates a lot of system calls being issued.
247 irq% Percentage of cpu time consumed for handling of device in‐
249 terrupts.
250 softirq% Percentage of cpu time consumed for soft interrupt han‐
252 dling.
253 steal% Percentage of cpu time stolen by other virtual machines
255 running on the same hardware.
256 guest% Percentage of cpu time used by other virtual machines run‐
258 ning on the same hardware (overlaps with usr%/nice%).
259 wait% Percentage of unused cpu time while at least one of the
261 processes in wait-state awaits completion of disk I/O.
262 idle% Percentage of unused cpu time because all processes are in
264 a wait-state but not waiting for disk-I/O.
265 The output for the flag -g contains the following columns per GPU:
267 busaddr GPU number and bus-ID (separated by '/').
269 gpubusy GPU busy percentage during interval.
271 membusy GPU memory busy percentage during interval, i.e. time to
273 issue read and write accesses on memory.
274 memocc Percentage of memory occupation at this moment.
276 memtot Total memory available.
278 memuse Used GPU memory at this moment.
280 gputype Type of GPU.
282 The output for the flag -p contains the following values:
284 pswch/s Number of process switches (also called context switches)
286 per second on this cpu. A process switch occurs at the mo‐
287 ment that an active thread (i.e. the thread using a cpu)
288 enters a wait state or has used its time slice completely;
289 another thread will then be chosen to use the cpu.
290 devintr/s Number of hardware interrupts handled per second on this
292 cpu.
293 clones/s The number of new threads started per second.
295 loadavg1 Load average reflecting the average number of threads in
297 the runqueue or in non-interruptible wait state (usually
298 waiting for disk or tape I/O) during the last minute.
299 loadavg5 Load average reflecting the average number of threads in
301 the runqueue or in non-interruptible wait state (usually
302 waiting for disk or tape I/O) during the last 5 minutes.
303 loadavg15 Load average reflecting the average number of threads in
305 the runqueue or in non-interruptible wait state (usually
306 waiting for disk or tape I/O) during the last 15 minutes.
307 The output for the flag -P contains information about the processes and
309 threads:
310 clones/s The number of new threads started per second.
312 pexit/s
314 curproc Total number of processes present in the system.
316 curzomb Number of zombie processes present in the system.
318 thrrun Total number of threads present in the system in state
320 'running'.
321 thrslpi Total number of threads present in the system in state 'in‐
323 terruptible sleeping'.
324 thrslpu Total number of threads present in the system in state 'un‐
326 interruptible sleeping'.
327 The output for the flag -m contains information about the memory- and
329 swap-utilization:
330 memtotal Total usable main memory size.
332 memfree Available main memory size at this moment (snapshot).
334 buffers Main memory used at this moment to cache metadata-blocks
336 (snapshot).
337 cached Main memory used at this moment to cache data-blocks (snap‐
339 shot).
340 dirty Amount of memory in the page cache that still has to be
342 flushed to disk at this moment (snapshot).
343 slabmem Main memory used at this moment for dynamically allocated
345 memory by the kernel (snapshot).
346 swptotal Total swap space size at this moment (snapshot).
348 swpfree Available swap space at this moment (snapshot).
350 The output for the flag -s contains information about the frequency of
352 swapping:
353 pagescan/s Number of scanned pages per second due to the fact that
355 free memory drops below a particular threshold.
356 swapin/s The number of memory-pages the system read from the swap-
358 device per second.
359 swapout/s The number of memory-pages the system wrote to the swap-de‐
361 vice per second.
362 oomkill The number of processes being killed during the last inter‐
364 val due to lack of memory/swap. The value -1 means that
365 this counter is not supported by the current kernel ver‐
366 sion.
367 commitspc The committed virtual memory space i.e. the reserved vir‐
369 tual space for all allocations of private memory space for
370 processes.
371 commitlim The maximum limit for the committed space, which is by de‐
373 fault swap size plus 50% of memory size. The kernel only
374 verifies whether the committed space exceeds the limit if
375 strict overcommit handling is configured (vm.overcom‐
376 mit_memory is 2).
377 The output for the flag -B contains the Pressure Stall Information
379 (PSI):
380 cpusome Average pressure percentage during the interval for the
382 category 'CPU some'.
383 memsome Average pressure percentage during the interval for the
385 category 'memory some'.
386 memfull Average pressure percentage during the interval for the
388 category 'memory full'.
389 iosome Average pressure percentage during the interval for the
391 category 'I/O some'.
392 iofull Average pressure percentage during the interval for the
394 category 'I/O full'.
395 The output for the flags -l (LVM), -f (MD), and -d (hard disk) contains
397 the following columns per active unit:
398 disk Name.
400 busy Busy-percentage of the unit (i.e. the portion of time that
402 the device was busy handling requests).
403 read/s Number of read-requests issued per second on this unit.
405 KB/read Average number of Kbytes transferred per read-request for
407 this unit.
408 writ/s Number of write-requests (including discard requests) is‐
410 sued per second on this unit.
411 KB/writ Average number of Kbytes transferred per write-request for
413 this unit.
414 avque Average number of requests outstanding in the queue during
416 the time that the unit is busy.
417 avserv Average number of milliseconds needed by a request on this
419 unit (seek, latency and data-transfer).
420 The output for the flag -n contains information about activity on NFS
422 mounted filesystems (client):
423 mounted_device
425 Mounted device containing server name and server directory
426 being mounted.
427 physread/s Kilobytes data physically read from the NFS server by pro‐
429 cesses running on the NFS client.
430 KBwrite/s Kilobytes data physically written to the NFS server by pro‐
432 cesses running on the NFS client.
433 When the NFS filesystem was mounted during the interval,
434 the state 'M' is shown.
435 The output for the flag -j contains information about NFS client activ‐
437 ity:
438 rpc/s Number of RPC calls per second issued to NFS server(s).
440 rpcread/s Number of read RPC calls per second issued to NFS
442 server(s).
443 rpcwrite/s Number of write RPC calls per second issued to NFS
445 server(s).
446 retrans/s Number of retransmitted RPC calls per second.
448 autrefresh/s
450 Number of authorization refreshes per second.
451 The output for the flag -J contains information about NFS server activ‐
453 ity:
454 rpc/s Number of RPC calls per second received from NFS client(s).
456 rpcread/s Number of read RPC calls per second received from NFS
458 client(s).
459 rpcwrite/s Number of write RPC calls per second received from NFS
461 client(s).
462 MBcr/s Number of Megabytes per second returned to read requests by
464 clients.
465 MBcw/s Number of Megabytes per second passed in write requests by
467 clients.
468 nettcp/s Number of requests per second handled via TCP.
470 netudp/s Number of requests per second handled via UDP.
472 The output for the flag -i provides information about utilization of
474 network interfaces:
475 interf Name of interface.
477 busy Busy percentage for this interface. If the linespeed of
479 this interface could not be determined (e.g. for virtual
480 interfaces), a question mark is shown.
481 ipack/s Number of packets received from this interface per second.
483 opack/s Number of packets transmitted to this interface per second.
485 iKbyte/s Number of Kbytes received from this interface per second.
487 oKbyte/s Number of Kbytes transmitted via this interface per second.
489 imbps/s Effective number of megabits received per second.
491 ombps/s Effective number of megabits transmitted per second.
493 maxmbps/s Linespeed as number of megabits per second. If the line‐
495 speed could not be determined (e.g. virtual interfaces),
496 value 0 is shown.
497 The linespeed is followed by the indication 'f' (full du‐
498 plex) or 'h' (half duplex).
499 The output for the flag -I provides information about the failures that
501 were detected for network interfaces:
502 interf Name of interface.
504 ierr/s Number of bad packets received from this interface per sec‐
506 ond.
507 oerr/s Number of times that packet transmission to this interface
509 failed per second.
510 coll/s Number of collisions encountered per second while transmit‐
512 ting packets.
513 idrop/s Number of received packets dropped per second due to lack
515 of buffer-space in the local system.
516 odrop/s Number of transmitted packets dropped per second due to
518 lack of buffer-space in the local system.
519 iframe/s Number of frame alignment-errors encountered per second on
521 received packets.
522 ocarrier/s Number of carrier-errors encountered per second on trans‐
524 mitted packets.
525 The output for the flag -w provides information about the utilization
527 of the IPv4-layer (formal SNMP-names between brackets):
528 inrecv/s Number of IP datagrams received from interfaces per second,
530 including those received in error (ipInReceives).
531 outreq/s Number of IP datagrams that local higher-layer protocols
533 supplied to IP in requests for transmission per second
534 (ipOutRequests).
535 indeliver/s Number of received IP datagrams that have been successfully
537 delivered to higher protocol-layers per second (ipInDeliv‐
538 ers).
539 forward/s Number of received IP datagrams per second for which this
541 entity was not their final IP destination, as a result of
542 which an attempt was made to forward (ipForwDatagrams).
543 reasmok/s Number of IP datagrams successfully reassembled per second
545 (ipReasmOKs).
546 fragcreat/s Number of IP datagram fragments generated per second at
548 this entity (ipFragCreates).
549 The output for the flag -W provides information about the failures that
551 were detected in the IPv4-layer (formal SNMP-names between brackets):
552 in: dsc/s Number of input IP datagrams per second for which no prob‐
554 lems were encountered to prevent their continued processing
555 but that were discarded, e.g. for lack of buffer space
556 (ipInDiscards).
557 in: hder/s Number of input IP datagrams per second discarded due to
559 errors in the IP header (ipInHdrErrors).
560 in: ader/s Number of input IP datagrams per second discarded because
562 the IP address in the destination field was not valid to be
563 received by this entity (ipInAddrErrors).
564 in: unkp/s Number of inbound packets per second that were discarded
566 because of an unknown or unsupported protocol (ipInUnknown‐
567 Protos).
568 in: ratim/s Number of timeout-situations per second while other frag‐
570 ments were expected for successful reassembly (ipReasmTime‐
571 out).
572 in: rfail/s Number of failures detected per second by the IP reassembly
574 algorithm (ipReasmFails).
575 out: dsc/s Number of output IP datagrams per second for which no prob‐
577 lems were encountered to prevent their continued processing
578 but that were discarded, e.g. for lack of buffer space
579 (ipOutDiscards).
580 out: nrt/s Number of IP datagrams per second discarded because no
582 route could be found (ipOutNoRoutes).
583 The output for the flag -y provides information about the general uti‐
585 lization of the ICMPv4-layer and some information per type of ICMP-mes‐
586 sage (formal SNMP-names between brackets):
587 intot/s Number of ICMP messages (any type) received per second at
589 this entity (icmpInMsgs).
590 outtot/s Number of ICMP messages (any type) transmitted per second
592 from this entity (icmpOutMsgs).
593 inecho/s Number of ICMP Echo (request) messages received per second
595 (icmpInEchos).
596 inerep/s Number of ICMP Echo-Reply messages received per second
598 (icmpInEchoReps).
599 otecho/s Number of ICMP Echo (request) messages transmitted per sec‐
601 ond (icmpOutEchos).
602 oterep/s Number of ICMP Echo-Reply messages transmitted per second
604 (icmpOutEchoReps).
605 The output for the flag -Y provides information about other types of
607 ICMPv4-messages (formal SNMP-names between brackets):
608 ierr/s Number of ICMP messages received per second but determined
610 to have ICMP-specific errors (icmpInErrors).
611 isq/s Number of ICMP Source Quench messages received per second
613 (icmpInSrcQuenchs).
614 ird/s Number of ICMP Redirect messages received per second (icmp‐
616 InRedirects).
617 idu/s Number of ICMP Destination Unreachable messages received
619 per second (icmpInDestUnreachs).
620 ite/s Number of ICMP Time Exceeded messages received per second
622 (icmpOutTimeExcds).
623 oerr/s Number of ICMP messages transmitted per second but deter‐
625 mined to have ICMP-specific errors (icmpOutErrors).
626 osq/s Number of ICMP Source Quench messages transmitted per sec‐
628 ond (icmpOutSrcQuenchs).
629 ord/s Number of ICMP Redirect messages transmitted per second
631 (icmpOutRedirects).
632 odu/s Number of ICMP Destination Unreachable messages transmitted
634 per second (icmpOutDestUnreachs).
635 ote/s Number of ICMP Time Exceeded messages transmitted per sec‐
637 ond (icmpOutTimeExcds).
638 The output for the flag -u provides information about the utilization
640 of the UDPv4-layer (formal SNMP-names between brackets):
641 indgram/s Number of UDP datagrams per second delivered to UDP users
643 (udpInDatagrams).
644 outdgram/s Number of UDP datagrams transmitted per second from this
646 entity (udpOutDatagrams).
647 inerr/s Number of received UDP datagrams per second that could not
649 be delivered for reasons other than the lack of an applica‐
650 tion at the destination port (udpInErrors).
651 noport/s Number of received UDP datagrams per second for which there
653 was no application at the destination port (udpNoPorts).
654 The output for the flag -z provides information about the utilization
656 of the IPv6-layer (formal SNMP-names between brackets):
657 inrecv/s Number of input IPv6-datagrams received from interfaces per
659 second, including those received in error (ipv6IfStatsInRe‐
660 ceives).
661 outreq/s Number of IPv6-datagrams per second that local higher-layer
663 protocols supplied to IP in requests for transmission
664 (ipv6IfStatsOutRequests). This counter does not include
665 any forwarded datagrams.
666 inmc/s Number of multicast packets per second that have been re‐
668 ceived by the interface (ipv6IfStatsInMcastPkts).
669 outmc/s Number of multicast packets per second that have been
671 transmitted to the interface (ipv6IfStatsOutMcastPkts).
672 indeliv/s Number of IP datagrams successfully delivered per second to
674 IPv6 user-protocols, including ICMP (ipv6IfStatsInDeliv‐
675 ers).
676 reasmok/s Number of IPv6 datagrams successfully reassembled per sec‐
678 ond (ipv6IfStatsReasmOKs).
679 fragcre/s Number of IPv6 datagram fragments generated per second at
681 this entity (ipv6IfStatsOutFragCreates).
682 The output for the flag -Z provides information about the failures that
684 were detected in the IPv6-layer (formal SNMP-names between brackets):
685 in: dsc/s Number of input IPv6 datagrams per second for which no
687 problems were encountered to prevent their continued pro‐
688 cessing but that were discarded, e.g. for lack of buffer
689 space (ipv6IfStatsInDiscards).
690 in: hder/s Number of input datagrams per second discarded due to er‐
692 rors in the IPv6 header (ipv6IfStatsInHdrErrors).
693 in: ader/s Number of input datagrams per second discarded because the
695 IPv6 address in the destination field was not valid to be
696 received by this entity (ipv6IfStatsInAddrErrors).
697 in: unkp/s Number of locally-addressed datagrams per second that were
699 discarded because of an unknown or unsupported protocol
700 (ipv6IfStatsInUnknownProtos).
701 in: ratim/s Number of timeout-situations per second while other IPv6
703 fragments were expected for successful reassembly
704 (ipv6ReasmTimeout).
705 in: rfail/s Number of failures detected per second by the IPv6 reassem‐
707 bly-algorithm (ipv6IfStatsReasmFails).
708 out: dsc/s Number of output IPv6 datagrams per second for which no
710 problems were encountered to prevent their continued pro‐
711 cessing but that were discarded, e.g. for lack of buffer
712 space (ipv6IfStatsOutDiscards).
713 out: nrt/s Number of IPv6 datagrams per second discarded because no
715 route could be found (ipv6IfStatsInNoRoutes).
716 The output for the flag -k provides information about the general uti‐
718 lization of the ICMPv6-layer and some information per type of ICMP-mes‐
719 sage (formal SNMP-names between brackets):
720 intot/s Number of ICMPv6 messages (any type) received per second at
722 the interface (ipv6IfIcmpInMsgs).
723 outtot/s Number of ICMPv6 messages (any type) transmitted per second
725 from this entity (ipv6IfIcmpOutMsgs).
726 inerr/s Number of ICMPv6 messages received per second that had
728 ICMP-specific errors, such as bad ICMP checksums, bad
729 length, etc (ipv6IfIcmpInErrors).
730 innsol/s Number of ICMP Neighbor Solicit messages received per sec‐
732 ond (ipv6IfIcmpInNeighborSolicits).
733 innadv/s Number of ICMP Neighbor Advertisement messages received per
735 second (ipv6IfIcmpInNeighborAdvertisements).
736 otnsol/s Number of ICMP Neighbor Solicit messages transmitted per
738 second (ipv6IfIcmpOutNeighborSolicits).
739 otnadv/s Number of ICMP Neighbor Advertisement messages transmitted
741 per second (ipv6IfIcmpOutNeighborAdvertisements).
742 The output for the flag -K provides information about other types of
744 ICMPv6-messages (formal SNMP-names between brackets):
745 iecho/s Number of ICMP Echo (request) messages received per second
747 (ipv6IfIcmpInEchos).
748 ierep/s Number of ICMP Echo-Reply messages received per second
750 (ipv6IfIcmpInEchoReplies).
751 oerep/s Number of ICMP Echo-Reply messages transmitted per second
753 (ipv6IfIcmpOutEchoReplies).
754 idu/s Number of ICMP Destination Unreachable messages received
756 per second (ipv6IfIcmpInDestUnreachs).
757 odu/s Number of ICMP Destination Unreachable messages transmitted
759 per second (ipv6IfIcmpOutDestUnreachs).
760 ird/s Number of ICMP Redirect messages received per second
762 (ipv6IfIcmpInRedirects).
763 ord/s Number of ICMP Redirect messages transmitted per second
765 (ipv6IfIcmpOutRedirect).
766 ite/s Number of ICMP Time Exceeded messages received per second
768 (ipv6IfIcmpInTimeExcds).
769 ote/s Number of ICMP Time Exceeded messages transmitted per sec‐
771 ond (ipv6IfIcmpOutTimeExcds).
772 The output for the flag -U provides information about the utilization
774 of the UDPv6-layer (formal SNMP-names between brackets):
775 indgram/s Number of UDPv6 datagrams per second delivered to UDP users
777 (udpInDatagrams),
778 outdgram/s Number of UDPv6 datagrams transmitted per second from this
780 entity (udpOutDatagrams),
781 inerr/s Number of received UDPv6 datagrams per second that could
783 not be delivered for reasons other than the lack of an ap‐
784 plication at the destination port (udpInErrors).
785 noport/s Number of received UDPv6 datagrams per second for which
787 there was no application at the destination port (udpNo‐
788 Ports).
789 The output for the flag -t provides information about the utilization
791 of the TCP-layer (formal SNMP-names between brackets):
792 insegs/s Number of received segments per second, including those re‐
794 ceived in error (tcpInSegs).
795 outsegs/s Number of transmitted segments per second, excluding those
797 containing only retransmitted octets (tcpOutSegs).
798 actopen/s Number of active opens per second that have been supported
800 by this entity (tcpActiveOpens).
801 pasopen/s Number of passive opens per second that have been supported
803 by this entity (tcpPassiveOpens).
804 nowopen Number of connections currently open (snapshot), for which
806 the state is either ESTABLISHED or CLOSE-WAIT (tcpCur‐
807 rEstab).
808 The output for the flag -T provides information about the failures that
810 were detected in the TCP-layer (formal SNMP-names between brackets):
811 inerr/s Number of received segments per second received in error
813 (tcpInErrs).
814 retrans/s Number of retransmitted segments per second (tcpRe‐
816 transSegs).
817 attfail/s Number of failed connection attempts per second that have
819 occurred at this entity (tcpAttemptFails).
820 estabreset/s
822 Number of resets per second that have occurred at this en‐
823 tity (tcpEstabResets).
824 outreset/s Number of transmitted segments per second containing the
826 RST flag (tcpOutRsts).
827 The output for the flag -h provides information about utilization of
829 Infiniband ports:
830 controller Name of controller.
832 port Controller port.
834 busy Busy percentage for this port.
836 ipack/s Number of packets received from this port per second.
838 opack/s Number of packets transmitted to this port per second.
840 igbps/s Effective number of gigabits received per second.
842 ogbps/s Effective number of gigabits transmitted per second.
844 maxgbps/s Maximum rate as number of gigabits per second.
846 lanes Number of lanes.
848 The output for the flag -O provides information about the top-3 of pro‐
850 cesses with the highest processor consumption:
851 pid Process-id (if zero, the process has exited while the pid
853 could not be determined).
854 command The name of the process.
856 cpu% The percentage of cpu-capacity being consumed. This value
858 can exceed 100% for a multithreaded process running on a
859 multiprocessor machine.
860 The output for the flag -G provides information about the top-3 of pro‐
862 cesses with the highest memory consumption:
863 pid Process-id (if zero, the process has exited while the pid
865 could not be determined).
866 command The name of the process.
868 mem% The percentage of resident memory-utilization by this
870 process.
871 The output for the flag -D provides information about the top-3 of pro‐
873 cesses that issue the most read and write accesses to disk:
874 pid Process-id (if zero, the process has exited while the pid
876 could not be determined).
877 command The name of the process.
879 dsk% The percentage of read and write accesses related to the
881 total number of read and write accesses issued on disk by
882 all processes, so a high percentage does not imply a high
883 disk load on system level.
884 The output for the flag -N provides information about the top-3 of pro‐
886 cesses that issue the most socket transfers for IPv4/IPv6:
887 pid Process-id (if zero, the process has exited while the pid
889 could not be determined).
890 command The name of the process.
892 net% The percentage of socket transfers related to the total
894 number of transfers issued by all processes, so a high per‐
895 centage does not imply a high network load on system level.
896
898 To see today's cpu-activity so far (supposed that atop is logging in
899 the background):
900 pcp-atopsar
902 To see the memory occupation for June 5, 2018 between 10:00 and 12:30
904 (supposed that pmlogger has been logging daily in the background on
905 host acme.com):
906 pcp-atopsar -m -r $PCP_LOG_DIR/pmlogger/acme.com/20180605 -b 10:00 -e
908 12:30
909 or
911 pcp-atopsar -m -r 20180605 -b 10:00 -e 12:30
913 or, suppose it is June 8, 2018 at this moment
915 pcp-atopsar -m -r yyy -b 10:00 -e 12:30
917 Write a logfile with atop to record the system behaviour for 30 minutes
919 (30 samples of one minute) and produce all available reports after‐
920 wards:
921 pcp-atop -w /tmp/atoplog 60 30
923 pcp-atopsar -A -r /tmp/atoplog
925 To watch TCP activity evolve for ten minutes (10 samples with sixty
927 seconds interval):
928 pcp-atopsar -t 60 10
930 To watch the header-lines ('_' as last character) of all reports with
932 only the detail-lines showing critical resource consumption (marker '*'
933 or '+' as last character):
934 pcp-atopsar -AM | grep '[_*+]$'
936
938 /etc/atoprc
939 Configuration file containing system-wide default values (mainly
940 flags). See related man-page.
941 ~/.atoprc
943 Configuration file containing personal default values (mainly
944 flags). See related man-page.
945 $PCP_LOG_DIR/pmlogger/HOST/YYYYMMDD
947 Daily data file, where YYYYMMDD are digits representing the date,
948 and HOST is the hostname of the machine being logged.
949
951 Environment variables with the prefix PCP_ are used to parameterize the
952 file and directory names used by PCP. On each installation, the file
953 /etc/pcp.conf contains the local values for these variables. The
954 $PCP_CONF variable may be used to specify an alternative configuration
955 file, as described in pcp.conf(5).
956 For environment variables affecting PCP tools, see pmGetOptions(3).
958
960 PCPIntro(1), pcp(1), pcp-atop(1), mkaf(1), pmlogger(1), pmlog‐
961 ger_daily(1) and pcp-atoprc(5).
962Performance Co-Pilot PCP PCP-ATOPSAR(1)