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 hh:mm] [-e 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 hh:mm.
33 In the second synopsis line, pcp-atopsar reads actual activity counters
35 from the kernel with the specified interval (in seconds) and the speci‐
36 fied number of samples (optionally). When pcp-atopsar is activated in
37 this way it immediately sends the output for every requested report to
38 standard output. If only one type of report is requested, the header
39 is printed once and after every interval seconds the statistical coun‐
40 ters are shown for that period. If several reports are requested, a
41 header is printed per sample followed by the statistical counters for
42 that period.
43 When invoked via the pcp(1) command, the PCPIntro(1) options -h/--host,
45 -a/--archive, -O/--origin, -s/--samples, -t/--interval, -Z/--timezone
46 and several other pcp options become indirectly available.
47 Some generic flags can be specified to influence the behaviour of the
49 pcp-atopsar program:
50 -S By default the timestamp at the beginning of a line is suppressed
52 if more lines are shown for one interval. With this flag a time‐
53 stamp is given for every output-line (easier for post-processing).
54 -a By default certain resources as disks and network interfaces are
56 only shown when they were active during the interval. With this
57 flag all resources of a given type are shown, even if they were
58 inactive during the interval.
59 -x By default pcp-atopsar only uses colors if output is directed to a
61 terminal (window). These colors might indicate that a critical
62 occupation percentage has been reached (red) or has been almost
63 reached (cyan) for a particular resource. See the man-page of
64 atop for a detailed description of this feature (section COLORS).
65 With the flag -x the use of colors is suppressed unconditionally.
66 -C By default pcp-atopsar only uses colors if output is directed to a
68 terminal (window). These colors might indicate that a critical
69 occupation percentage has been reached (red) or has been almost
70 reached (cyan) for a particular resource. See the man-page of
71 atop for a detailed description of this feature (section COLORS).
72 With the flag -C colors will always be used, even if output is not
73 directed to a terminal.
74 -M Use markers at the end of a line to indicate that a critical occu‐
76 pation percentage has been reached ('*') or has been almost
77 reached ('+') for particular resources. The marker '*' is similar
78 to the color red and the marker '+' to the color cyan. See the
79 man-page of atop for a detailed description of these colors (sec‐
80 tion COLORS).
81 -H Repeat the header line within a report for every N detail lines.
83 The value of N is determined dynamically in case of output to a
84 tty/window (depending on the number of lines); for output to a
85 file or pipe this value is 23.
86 -R Summarize cnt samples into one sample. When the logfile contains
88 e.g. samples of 10 minutes, the use of the flag '-R 6' shows a
89 report with one sample for every hour.
90 Other flags are used to define which reports are required:
92 -A Show all possible reports.
94 -c Report about CPU utilization (in total and per cpu).
96 -p Report about processor-related matters, like load-averages and
98 hardware interrupts.
99 -P Report about processes.
101 -m Current memory- and swap-occupation.
103 -s Report about paging- and swapping-activity, and overcommitment.
105 -l Report about utilization of logical volumes.
107 -f Report about utilization of multiple devices.
109 -d Report about utilization of disks.
111 -n Report about NFS mounted filesystems on NFS client.
113 -j Report about NFS client activity.
115 -J Report about NFS server activity.
117 -i Report about the network interfaces.
119 -I Report about errors for network-interfaces.
121 -w Report about IP version 4 network traffic.
123 -W Report about errors for IP version 4 traffic.
125 -y General report about ICMP version 4 layer activity.
127 -Y Per-type report about ICMP version 4 layer activity.
129 -u Report about UDP version 4 network traffic.
131 -z Report about IP version 6 network traffic.
133 -Z Report about errors for IP version 6 traffic.
135 -k General report about ICMP version 6 layer activity.
137 -K Per-type report about ICMP version 6 layer activity.
139 -U Report about UDP version 6 network traffic.
141 -t Report about TCP network traffic.
143 -T Report about errors for TCP-traffic.
145 -O Report about top-3 processes consuming most processor capacity.
147 This report is only available when using a log file (not when
148 specifying an interval).
149 -G Report about top-3 processes consuming most resident memory. This
151 report is only available when using a log file (not when specify‐
152 ing an interval).
153 -D Report about top-3 processes issueing most disk transfers. This
155 report is only available when using a log file (not when specify‐
156 ing an interval).
157 -N Report about top-3 processes issueing most IPv4/IPv6 socket trans‐
159 fers. This report is only available when using a log file (not
160 when specifying an interval).
161
163 Depending on the requested report, a number of columns with output val‐
164 ues are produced. The values are mostly presented as a number of
165 events per second.
166 The output for the flag -c contains the following columns per cpu:
168 usr% Percentage of cpu-time consumed in user mode (program text)
170 for all active processes running with a nice value of zero
171 (default) or a negative nice value (which means a higher
172 priority than usual). The cpu consumption in user mode of
173 processes with a nice value larger than zero (lower prior‐
174 ity) is indicated in the nice%-column.
175 nice% Percentage of cpu time consumed in user mode (i.e. program
177 text) for all processes running witn a nice value larger
178 than zero (which means with a lower priority than average).
179 sys% Percentage of cpu time consumed in system mode (kernel
181 text) for all active processes. A high percentage usually
182 indicates a lot of system calls being issued.
183 irq% Percentage of cpu time consumed for handling of device
185 interrupts.
186 softirq% Percentage of cpu time consumed for soft interrupt han‐
188 dling.
189 steal% Percentage of cpu time stolen by other virtual machines
191 running on the same hardware.
192 guest% Percentage of cpu time used by other virtual machines run‐
194 ning on the same hardware (overlaps with usr%/nice%).
195 wait% Percentage of unused cpu time while at least one of the
197 processes in wait-state awaits completion of disk I/O.
198 idle% Percentage of unused cpu time because all processes are in
200 a wait-state but not waiting for disk-I/O.
201 The output for the flag -p contains the following values:
203 pswch/s Number of process switches (also called context switches)
205 per second on this cpu. A process switch occurs at the
206 moment that an active thread (i.e. the thread using a cpu)
207 enters a wait state or has used its time slice completely;
208 another thread will then be chosen to use the cpu.
209 devintr/s Number of hardware interrupts handled per second on this
211 cpu.
212 clones/s The number of new threads started per second.
214 loadavg1 Load average reflecting the average number of threads in
216 the runqueue or in non-interruptible wait state (usually
217 waiting for disk or tape I/O) during the last minute.
218 loadavg5 Load average reflecting the average number of threads in
220 the runqueue or in non-interruptible wait state (usually
221 waiting for disk or tape I/O) during the last 5 minutes.
222 loadavg15 Load average reflecting the average number of threads in
224 the runqueue or in non-interruptible wait state (usually
225 waiting for disk or tape I/O) during the last 15 minutes.
226 The output for the flag -P contains information about the processes and
228 threads:
229 clones/s The number of new threads started per second.
231 pexit/s
233 curproc Total number of processes present in the system.
235 curzomb Number of zombie processes present in the system.
237 thrrun Total number of threads present in the system in state
239 'running'.
240 thrslpi Total number of threads present in the system in state
242 'interruptible sleeping'.
243 thrslpu Total number of threads present in the system in state
245 'uninterruptible sleeping'.
246 The output for the flag -m contains information about the memory- and
248 swap-utilization:
249 memtotal Total usable main memory size.
251 memfree Available main memory size at this moment (snapshot).
253 buffers Main memory used at this moment to cache metadata-blocks
255 (snapshot).
256 cached Main memory used at this moment to cache data-blocks (snap‐
258 shot).
259 dirty Amount of memory in the page cache that still has to be
261 flushed to disk at this moment (snapshot).
262 slabmem Main memory used at this moment for dynamically allocated
264 memory by the kernel (snapshot).
265 swptotal Total swap space size at this moment (snapshot).
267 swpfree Available swap space at this moment (snapshot).
269 The output for the flag -s contains information about the frequency of
271 swapping:
272 pagescan/s Number of scanned pages per second due to the fact that
274 free memory drops below a particular threshold.
275 swapin/s The number of memory-pages the system read from the swap-
277 device per second.
278 swapout/s The number of memory-pages the system wrote to the swap-
280 device per second.
281 commitspc The committed virtual memory space i.e. the reserved vir‐
283 tual space for all allocations of private memory space for
284 processes.
285 commitlim The maximum limit for the committed space, which is by
287 default swap size plus 50% of memory size. The kernel only
288 verifies whether the committed space exceeds the limit if
289 strict overcommit handling is configured (vm.overcom‐
290 mit_memory is 2).
291 The output for the flags -l (LVM), -f (MD), and -d (hard disk) contains
293 the following columns per active unit:
294 disk Name.
296 busy Busy-percentage of the unit (i.e. the portion of time that
298 the device was busy handling requests).
299 read/s Number of read-requests issued per second on this unit.
301 KB/read Average number of Kbytes transferred per read-request for
303 this unit.
304 writ/s Number of write-requests issued per second on this unit.
306 KB/writ Average number of Kbytes transferred per write-request for
308 this unit.
309 avque Average number of requests outstanding in the queue during
311 the time that the unit is busy.
312 avserv Average number of milliseconds needed by a request on this
314 unit (seek, latency and data-transfer).
315 The output for the flag -n contains information about activity on NFS
317 mounted filesystems (client):
318 mounted_device
320 Mounted device containing server name and server directory
321 being mounted.
322 physread/s Kilobytes data physically read from the NFS server by pro‐
324 cesses running on the NFS client.
325 KBwrite/s Kilobytes data physically written to the NFS server by pro‐
327 cesses running on the NFS client.
328 When the NFS filesystem was mounted during the interval,
329 the state 'M' is shown.
330 The output for the flag -j contains information about NFS client activ‐
332 ity:
333 rpc/s Number of RPC calls per second issued to NFS server(s).
335 rpcread/s Number of read RPC calls per second issued to NFS
337 server(s).
338 rpcwrite/s Number of write RPC calls per second issued to NFS
340 server(s).
341 retrans/s Number of retransmitted RPC calls per second.
343 autrefresh/s
345 Number of authorization refreshes per second.
346 The output for the flag -J contains information about NFS server activ‐
348 ity:
349 rpc/s Number of RPC calls per second received from NFS client(s).
351 rpcread/s Number of read RPC calls per second received from NFS
353 client(s).
354 rpcwrite/s Number of write RPC calls per second received from NFS
356 client(s).
357 MBcr/s Number of Megabytes per second returned to read requests by
359 clients.
360 MBcw/s Number of Megabytes per second passed in write requests by
362 clients.
363 nettcp/s Number of requests per second handled via TCP.
365 netudp/s Number of requests per second handled via UDP.
367 The output for the flag -i provides information about utilization of
369 network interfaces:
370 interf Name of interface.
372 busy Busy percentage for this interface. If the linespeed of
374 this interface could not be determined (e.g. for virtual
375 interfaces), a question mark is shown.
376 ipack/s Number of packets received from this interface per second.
378 opack/s Number of packets transmitted to this interface per second.
380 iKbyte/s Number of Kbytes received from this interface per second.
382 oKbyte/s Number of Kbytes transmitted via this interface per second.
384 imbps/s Effective number of megabits received per second.
386 ombps/s Effective number of megabits transmitted per second.
388 maxmbps/s Linespeed as number of megabits per second. If the line‐
390 speed could not be determined (e.g. virtual interfaces),
391 value 0 is shown.
392 The linespeed is followed by the indication 'f' (full
393 duplex) or 'h' (half duplex).
394 The output for the flag -I provides information about the failures that
396 were detected for network interfaces:
397 interf Name of interface.
399 ierr/s Number of bad packets received from this interface per sec‐
401 ond.
402 oerr/s Number of times that packet transmission to this interface
404 failed per second.
405 coll/s Number of collisions encountered per second while transmit‐
407 ting packets.
408 idrop/s Number of received packets dropped per second due to lack
410 of buffer-space in the local system.
411 odrop/s Number of transmitted packets dropped per second due to
413 lack of buffer-space in the local system.
414 iframe/s Number of frame alignment-errors encountered per second on
416 received packets.
417 ocarrier/s Number of carrier-errors encountered per second on trans‐
419 mitted packets.
420 The output for the flag -w provides information about the utilization
422 of the IPv4-layer (formal SNMP-names between brackets):
423 inrecv/s Number of IP datagrams received from interfaces per second,
425 including those received in error (ipInReceives).
426 outreq/s Number of IP datagrams that local higher-layer protocols
428 supplied to IP in requests for transmission per second
429 (ipOutRequests).
430 indeliver/s Number of received IP datagrams that have been successfully
432 delivered to higher protocol-layers per second (ipInDeliv‐
433 ers).
434 forward/s Number of received IP datagrams per second for which this
436 entity was not their final IP destination, as a result of
437 which an attempt was made to forward (ipForwDatagrams).
438 reasmok/s Number of IP datagrams successfully reassembled per second
440 (ipReasmOKs).
441 fragcreat/s Number of IP datagram fragments generated per second at
443 this entity (ipFragCreates).
444 The output for the flag -W provides information about the failures that
446 were detected in the IPv4-layer (formal SNMP-names between brackets):
447 in: dsc/s Number of input IP datagrams per second for which no prob‐
449 lems were encountered to prevent their continued processing
450 but that were discarded, e.g. for lack of buffer space
451 (ipInDiscards).
452 in: hder/s Number of input IP datagrams per second discarded due to
454 errors in the IP header (ipInHdrErrors).
455 in: ader/s Number of input IP datagrams per second discarded because
457 the IP address in the destination field was not valid to be
458 received by this entity (ipInAddrErrors).
459 in: unkp/s Number of inbound packets per second that were discarded
461 because of an unknown or unsupported protocol (ipInUnknown‐
462 Protos).
463 in: ratim/s Number of timeout-situations per second while other frag‐
465 ments were expected for successful reassembly (ipReasmTime‐
466 out).
467 in: rfail/s Number of failures detected per second by the IP reassembly
469 algorithm (ipReasmFails).
470 out: dsc/s Number of output IP datagrams per second for which no prob‐
472 lems were encountered to prevent their continued processing
473 but that were discarded, e.g. for lack of buffer space
474 (ipOutDiscards).
475 out: nrt/s Number of IP datagrams per second discarded because no
477 route could be found (ipOutNoRoutes).
478 The output for the flag -y provides information about the general uti‐
480 lization of the ICMPv4-layer and some information per type of ICMP-mes‐
481 sage (formal SNMP-names between brackets):
482 intot/s Number of ICMP messages (any type) received per second at
484 this entity (icmpInMsgs).
485 outtot/s Number of ICMP messages (any type) transmitted per second
487 from this entity (icmpOutMsgs).
488 inecho/s Number of ICMP Echo (request) messages received per second
490 (icmpInEchos).
491 inerep/s Number of ICMP Echo-Reply messages received per second
493 (icmpInEchoReps).
494 otecho/s Number of ICMP Echo (request) messages transmitted per sec‐
496 ond (icmpOutEchos).
497 oterep/s Number of ICMP Echo-Reply messages transmitted per second
499 (icmpOutEchoReps).
500 The output for the flag -Y provides information about other types of
502 ICMPv4-messages (formal SNMP-names between brackets):
503 ierr/s Number of ICMP messages received per second but determined
505 to have ICMP-specific errors (icmpInErrors).
506 isq/s Number of ICMP Source Quench messages received per second
508 (icmpInSrcQuenchs).
509 ird/s Number of ICMP Redirect messages received per second (icmp‐
511 InRedirects).
512 idu/s Number of ICMP Destination Unreachable messages received
514 per second (icmpInDestUnreachs).
515 ite/s Number of ICMP Time Exceeded messages received per second
517 (icmpOutTimeExcds).
518 oerr/s Number of ICMP messages transmitted per second but deter‐
520 mined to have ICMP-specific errors (icmpOutErrors).
521 osq/s Number of ICMP Source Quench messages transmitted per sec‐
523 ond (icmpOutSrcQuenchs).
524 ord/s Number of ICMP Redirect messages transmitted per second
526 (icmpOutRedirects).
527 odu/s Number of ICMP Destination Unreachable messages transmitted
529 per second (icmpOutDestUnreachs).
530 ote/s Number of ICMP Time Exceeded messages transmitted per sec‐
532 ond (icmpOutTimeExcds).
533 The output for the flag -u provides information about the utilization
535 of the UDPv4-layer (formal SNMP-names between brackets):
536 indgram/s Number of UDP datagrams per second delivered to UDP users
538 (udpInDatagrams).
539 outdgram/s Number of UDP datagrams transmitted per second from this
541 entity (udpOutDatagrams).
542 inerr/s Number of received UDP datagrams per second that could not
544 be delivered for reasons other than the lack of an applica‐
545 tion at the destination port (udpInErrors).
546 noport/s Number of received UDP datagrams per second for which there
548 was no application at the destination port (udpNoPorts).
549 The output for the flag -z provides information about the utilization
551 of the IPv6-layer (formal SNMP-names between brackets):
552 inrecv/s Number of input IPv6-datagrams received from interfaces per
554 second, including those received in error (ipv6IfStatsInRe‐
555 ceives).
556 outreq/s Number of IPv6-datagrams per second that local higher-layer
558 protocols supplied to IP in requests for transmission
559 (ipv6IfStatsOutRequests). This counter does not include
560 any forwarded datagrams.
561 inmc/s Number of multicast packets per second that have been
563 received by the interface (ipv6IfStatsInMcastPkts).
564 outmc/s Number of multicast packets per second that have been
566 transmitted to the interface (ipv6IfStatsOutMcastPkts).
567 indeliv/s Number of IP datagrams successfully delivered per second to
569 IPv6 user-protocols, including ICMP (ipv6IfStatsInDeliv‐
570 ers).
571 reasmok/s Number of IPv6 datagrams successfully reassembled per sec‐
573 ond (ipv6IfStatsReasmOKs).
574 fragcre/s Number of IPv6 datagram fragments generated per second at
576 this entity (ipv6IfStatsOutFragCreates).
577 The output for the flag -Z provides information about the failures that
579 were detected in the IPv6-layer (formal SNMP-names between brackets):
580 in: dsc/s Number of input IPv6 datagrams per second for which no
582 problems were encountered to prevent their continued pro‐
583 cessing but that were discarded, e.g. for lack of buffer
584 space (ipv6IfStatsInDiscards).
585 in: hder/s Number of input datagrams per second discarded due to
587 errors in the IPv6 header (ipv6IfStatsInHdrErrors).
588 in: ader/s Number of input datagrams per second discarded because the
590 IPv6 address in the destination field was not valid to be
591 received by this entity (ipv6IfStatsInAddrErrors).
592 in: unkp/s Number of locally-addressed datagrams per second that were
594 discarded because of an unknown or unsupported protocol
595 (ipv6IfStatsInUnknownProtos).
596 in: ratim/s Number of timeout-situations per second while other IPv6
598 fragments were expected for successful reassembly
599 (ipv6ReasmTimeout).
600 in: rfail/s Number of failures detected per second by the IPv6 reassem‐
602 bly-algorithm (ipv6IfStatsReasmFails).
603 out: dsc/s Number of output IPv6 datagrams per second for which no
605 problems were encountered to prevent their continued pro‐
606 cessing but that were discarded, e.g. for lack of buffer
607 space (ipv6IfStatsOutDiscards).
608 out: nrt/s Number of IPv6 datagrams per second discarded because no
610 route could be found (ipv6IfStatsInNoRoutes).
611 The output for the flag -k provides information about the general uti‐
613 lization of the ICMPv6-layer and some information per type of ICMP-mes‐
614 sage (formal SNMP-names between brackets):
615 intot/s Number of ICMPv6 messages (any type) received per second at
617 the interface (ipv6IfIcmpInMsgs).
618 outtot/s Number of ICMPv6 messages (any type) transmitted per second
620 from this entity (ipv6IfIcmpOutMsgs).
621 inerr/s Number of ICMPv6 messages received per second that had
623 ICMP-specific errors, such as bad ICMP checksums, bad
624 length, etc (ipv6IfIcmpInErrors).
625 innsol/s Number of ICMP Neighbor Solicit messages received per sec‐
627 ond (ipv6IfIcmpInNeighborSolicits).
628 innadv/s Number of ICMP Neighbor Advertisement messages received per
630 second (ipv6IfIcmpInNeighborAdvertisements).
631 otnsol/s Number of ICMP Neighbor Solicit messages transmitted per
633 second (ipv6IfIcmpOutNeighborSolicits).
634 otnadv/s Number of ICMP Neighbor Advertisement messages transmitted
636 per second (ipv6IfIcmpOutNeighborAdvertisements).
637 The output for the flag -K provides information about other types of
639 ICMPv6-messages (formal SNMP-names between brackets):
640 iecho/s Number of ICMP Echo (request) messages received per second
642 (ipv6IfIcmpInEchos).
643 ierep/s Number of ICMP Echo-Reply messages received per second
645 (ipv6IfIcmpInEchoReplies).
646 oerep/s Number of ICMP Echo-Reply messages transmitted per second
648 (ipv6IfIcmpOutEchoReplies).
649 idu/s Number of ICMP Destination Unreachable messages received
651 per second (ipv6IfIcmpInDestUnreachs).
652 odu/s Number of ICMP Destination Unreachable messages transmitted
654 per second (ipv6IfIcmpOutDestUnreachs).
655 ird/s Number of ICMP Redirect messages received per second
657 (ipv6IfIcmpInRedirects).
658 ord/s Number of ICMP Redirect messages transmitted per second
660 (ipv6IfIcmpOutRedirect).
661 ite/s Number of ICMP Time Exceeded messages received per second
663 (ipv6IfIcmpInTimeExcds).
664 ote/s Number of ICMP Time Exceeded messages transmitted per sec‐
666 ond (ipv6IfIcmpOutTimeExcds).
667 The output for the flag -U provides information about the utilization
669 of the UDPv6-layer (formal SNMP-names between brackets):
670 indgram/s Number of UDPv6 datagrams per second delivered to UDP users
672 (udpInDatagrams),
673 outdgram/s Number of UDPv6 datagrams transmitted per second from this
675 entity (udpOutDatagrams),
676 inerr/s Number of received UDPv6 datagrams per second that could
678 not be delivered for reasons other than the lack of an
679 application at the destination port (udpInErrors).
680 noport/s Number of received UDPv6 datagrams per second for which
682 there was no application at the destination port (udpNo‐
683 Ports).
684 The output for the flag -t provides information about the utilization
686 of the TCP-layer (formal SNMP-names between brackets):
687 insegs/s Number of received segments per second, including those
689 received in error (tcpInSegs).
690 outsegs/s Number of transmitted segments per second, excluding those
692 containing only retransmitted octets (tcpOutSegs).
693 actopen/s Number of active opens per second that have been supported
695 by this entity (tcpActiveOpens).
696 pasopen/s Number of passive opens per second that have been supported
698 by this entity (tcpPassiveOpens).
699 nowopen Number of connections currently open (snapshot), for which
701 the state is either ESTABLISHED or CLOSE-WAIT (tcpCur‐
702 rEstab).
703 The output for the flag -T provides information about the failures that
705 were detected in the TCP-layer (formal SNMP-names between brackets):
706 inerr/s Number of received segments per second received in error
708 (tcpInErrs).
709 retrans/s Number of retransmitted segments per second (tcpRe‐
711 transSegs).
712 attfail/s Number of failed connection attempts per second that have
714 occurred at this entity (tcpAttemptFails).
715 estabreset/s
717 Number of resets per second that have occurred at this
718 entity (tcpEstabResets).
719 outreset/s Number of transmitted segments per second containing the
721 RST flag (tcpOutRsts).
722 The output for the flag -O provides information about the top-3 of pro‐
724 cesses with the highest processor consumption:
725 pid Process-id (if zero, the process has exited while the pid
727 could not be determined).
728 command The name of the process.
730 cpu% The percentage of cpu-capacity being consumed. This value
732 can exceed 100% for a multithreaded process running on a
733 multiprocessor machine.
734 The output for the flag -G provides information about the top-3 of pro‐
736 cesses with the highest memory consumption:
737 pid Process-id (if zero, the process has exited while the pid
739 could not be determined).
740 command The name of the process.
742 mem% The percentage of resident memory-utilization by this
744 process.
745 The output for the flag -D provides information about the top-3 of pro‐
747 cesses that issue the most read and write accesses to disk:
748 pid Process-id (if zero, the process has exited while the pid
750 could not be determined).
751 command The name of the process.
753 dsk% The percentage of read and write accesses related to the
755 total number of read and write accesses issued on disk by
756 all processes, so a high percentage does not imply a high
757 disk load on system level.
758 The output for the flag -N provides information about the top-3 of pro‐
760 cesses that issue the most socket transfers for IPv4/IPv6:
761 pid Process-id (if zero, the process has exited while the pid
763 could not be determined).
764 command The name of the process.
766 net% The percentage of socket transfers related to the total
768 number of transfers issued by all processes, so a high per‐
769 centage does not imply a high network load on system level.
770
772 To see today's cpu-activity so far (supposed that atop is logging in
773 the background):
774 pcp-atopsar
776 To see the memory occupation for June 5, 2012 between 10:00 and 12:30
778 (supposed that pmlogger has been logging daily in the background on
779 host acme.com):
780 pcp-atopsar -m -r $PCP_LOG_DIR/pmlogger/acme.com/20120605 -b 10:00 -e
782 12:30
783 or
785 pcp-atopsar -m -r 20120605 -b 10:00 -e 12:30
787 or, suppose it is June 8, 2012 at this moment
789 pcp-atopsar -m -r yyy -b 10:00 -e 12:30
791 Write a logfile with atop to record the system behaviour for 30 minutes
793 (30 samples of one minute) and produce all available reports after‐
794 wards:
795 pcp-atop -w /tmp/atoplog 60 30
797 pcp-atopsar -A -r /tmp/atoplog
799 To watch TCP activity evolve for ten minutes (10 samples with sixty
801 seconds interval):
802 pcp-atopsar -t 60 10
804 To watch the header-lines ('_' as last character) of all reports with
806 only the detail-lines showing critical resource consumption (marker '*'
807 or '+' as last character):
808 pcp-atopsar -AM | grep '[_*+]$'
810
812 /etc/atoprc
813 Configuration file containing system-wide default values (mainly
814 flags). See related man-page.
815 ~/.atoprc
817 Configuration file containing personal default values (mainly
818 flags). See related man-page.
819 $PCP_LOG_DIR/pmlogger/HOST/YYYYMMDD
821 Daily data file, where YYYYMMDD are digits representing the date,
822 and HOST is the hostname of the machine being logged.
823
825 pcp(1), pcp-atop(1), mkaf(1), pmlogger(1), pmlogger_daily(1), PCPIn‐
826 tro(1) and pcp-atoprc(5).
827Performance Co-Pilot PCP PCP-ATOPSAR(1)