1ATOPSAR(1) General Commands Manual ATOPSAR(1)
2
6 atopsar - Advanced System Activity Report (atop related)
7
9 atopsar [-flags...] [-r file|date ] [-R cnt ] [-b hh:mm ] [-e hh:mm ]
10 atopsar [-flags...] interval [ samples ]
11
13 The program atopsar can be used to report statistics on system level.
14 In the first synopsis line (no sampling interval specified), atopsar
16 extracts data from a raw logfile that has been recorded previously by
17 the program atop (option -w of the atop program).
18 You can specify the name of the logfile with the -r option of the atop‐
19 sar program. When a daily logfile of atop is used, named
20 /var/log/atop/atop_YYYYMMDD (where YYYYMMDD reflects the date), the
21 required date of the form YYYYMMDD can be specified with the -r option
22 instead of the filename, or the symbolic name 'y' can be used for yes‐
23 terday's daily logfile (this can be repeated so 'yyyy' indicates the
24 logfile of four days ago). If the -r option is not specified at all,
25 today's daily logfile is used by default.
26 The starting and ending times of the report can be defined using the
27 options -b and -e followed by a time argument of the form hh:mm.
28 In the second synopsis line, atopsar reads actual activity counters
30 from the kernel with the specified interval (in seconds) and the speci‐
31 fied number of samples (optionally). When atopsar is activated in this
32 way it immediately sends the output for every requested report to stan‐
33 dard output. If only one type of report is requested, the header is
34 printed once and after every interval seconds the statistical counters
35 are shown for that period. If several reports are requested, a header
36 is printed per sample followed by the statistical counters for that
37 period.
38 Some generic flags can be specified to influence the behaviour of the
40 atopsar program:
41 -S By default the timestamp at the beginning of a line is suppressed
43 if more lines are shown for one interval. With this flag a time‐
44 stamp is given for every output-line (easier for post-processing).
45 -a By default certain resources as disks and network interfaces are
47 only shown when they were active during the interval. With this
48 flag all resources of a given type are shown, even if they were
49 inactive during the interval.
50 -x By default atopsar only uses colors if output is directed to a
52 terminal (window). These colors might indicate that a critical
53 occupation percentage has been reached (red) or has been almost
54 reached (cyan) for a particular resource. See the man-page of
55 atop for a detailed description of this feature (section COLORS).
56 With the flag -x the use of colors is suppressed unconditionally.
57 -C By default atopsar only uses colors if output is directed to a
59 terminal (window). These colors might indicate that a critical
60 occupation percentage has been reached (red) or has been almost
61 reached (cyan) for a particular resource. See the man-page of
62 atop for a detailed description of this feature (section COLORS).
63 With the flag -C colors will always be used, even if output is not
64 directed to a terminal.
65 -M Use markers at the end of a line to indicate that a critical occu‐
67 pation percentage has been reached ('*') or has been almost
68 reached ('+') for particular resources. The marker '*' is similar
69 to the color red and the marker '+' to the color cyan. See the
70 man-page of atop for a detailed description of these colors (sec‐
71 tion COLORS).
72 -H Repeat the header line within a report for every N detail lines.
74 The value of N is determined dynamically in case of output to a
75 tty/window (depending on the number of lines); for output to a
76 file or pipe this value is 23.
77 -R Summarize cnt samples into one sample. When the logfile contains
79 e.g. samples of 10 minutes, the use of the flag '-R 6' shows a
80 report with one sample for every hour.
81 Other flags are used to define which reports are required:
83 -A Show all possible reports.
85 -c Report about CPU utilization (in total and per cpu).
87 -p Report about processor-related matters, like load-averages and
89 hardware interrupts.
90 -P Report about processes.
92 -m Current memory- and swap-occupation.
94 -s Report about paging- and swapping-activity, and overcommitment.
96 -l Report about utilization of logical volumes.
98 -f Report about utilization of multiple devices.
100 -d Report about utilization of disks.
102 -n Report about NFS mounted filesystems on NFS client.
104 -j Report about NFS client activity.
106 -J Report about NFS server activity.
108 -i Report about the network interfaces.
110 -I Report about errors for network-interfaces.
112 -w Report about IP version 4 network traffic.
114 -W Report about errors for IP version 4 traffic.
116 -y General report about ICMP version 4 layer activity.
118 -Y Per-type report about ICMP version 4 layer activity.
120 -u Report about UDP version 4 network traffic.
122 -z Report about IP version 6 network traffic.
124 -Z Report about errors for IP version 6 traffic.
126 -k General report about ICMP version 6 layer activity.
128 -K Per-type report about ICMP version 6 layer activity.
130 -U Report about UDP version 6 network traffic.
132 -t Report about TCP network traffic.
134 -T Report about errors for TCP-traffic.
136 -O Report about top-3 processes consuming most processor capacity.
138 This report is only available when using a log file (not when
139 specifying an interval).
140 -G Report about top-3 processes consuming most resident memory. This
142 report is only available when using a log file (not when specify‐
143 ing an interval).
144 -D Report about top-3 processes issueing most disk transfers. This
146 report is only available when using a log file (not when specify‐
147 ing an interval).
148 -N Report about top-3 processes issueing most IPv4/IPv6 socket trans‐
150 fers. This report is only available when using a log file (not
151 when specifying an interval).
152
154 Depending on the requested report, a number of columns with output val‐
155 ues are produced. The values are mostly presented as a number of
156 events per second.
157 The output for the flag -c contains the following columns per cpu:
159 usr% Percentage of cpu-time consumed in user mode (program text)
161 for all active processes running with a nice value of zero
162 (default) or a negative nice value (which means a higher
163 priority than usual). The cpu consumption in user mode of
164 processes with a nice value larger than zero (lower prior‐
165 ity) is indicated in the nice%-column.
166 nice% Percentage of cpu time consumed in user mode (i.e. program
168 text) for all processes running witn a nice value larger
169 than zero (which means with a lower priority than average).
170 sys% Percentage of cpu time consumed in system mode (kernel
172 text) for all active processes. A high percentage usually
173 indicates a lot of system calls being issued.
174 irq% Percentage of cpu time consumed for handling of device
176 interrupts.
177 softirq% Percentage of cpu time consumed for soft interrupt han‐
179 dling.
180 steal% Percentage of cpu time stolen by other virtual machines
182 running on the same hardware.
183 guest% Percentage of cpu time used by other virtual machines run‐
185 ning on the same hardware (overlaps with usr%/nice%).
186 wait% Percentage of unused cpu time while at least one of the
188 processes in wait-state awaits completion of disk I/O.
189 idle% Percentage of unused cpu time because all processes are in
191 a wait-state but not waiting for disk-I/O.
192 The output for the flag -p contains the following values:
194 pswch/s Number of process switches (also called context switches)
196 per second on this cpu. A process switch occurs at the
197 moment that an active thread (i.e. the thread using a cpu)
198 enters a wait state or has used its time slice completely;
199 another thread will then be chosen to use the cpu.
200 devintr/s Number of hardware interrupts handled per second on this
202 cpu.
203 clones/s The number of new threads started per second.
205 loadavg1 Load average reflecting the average number of threads in
207 the runqueue or in non-interruptible wait state (usually
208 waiting for disk or tape I/O) during the last minute.
209 loadavg5 Load average reflecting the average number of threads in
211 the runqueue or in non-interruptible wait state (usually
212 waiting for disk or tape I/O) during the last 5 minutes.
213 loadavg15 Load average reflecting the average number of threads in
215 the runqueue or in non-interruptible wait state (usually
216 waiting for disk or tape I/O) during the last 15 minutes.
217 The output for the flag -P contains information about the processes and
219 threads:
220 clones/s The number of new threads started per second.
222 pexit/s
224 curproc Total number of processes present in the system.
226 curzomb Number of zombie processes present in the system.
228 thrrun Total number of threads present in the system in state
230 'running'.
231 thrslpi Total number of threads present in the system in state
233 'interruptible sleeping'.
234 thrslpu Total number of threads present in the system in state
236 'uninterruptible sleeping'.
237 The output for the flag -m contains information about the memory- and
239 swap-utilization:
240 memtotal Total usable main memory size.
242 memfree Available main memory size at this moment (snapshot).
244 buffers Main memory used at this moment to cache metadata-blocks
246 (snapshot).
247 cached Main memory used at this moment to cache data-blocks (snap‐
249 shot).
250 dirty Amount of memory in the page cache that still has to be
252 flushed to disk at this moment (snapshot).
253 slabmem Main memory used at this moment for dynamically allocated
255 memory by the kernel (snapshot).
256 swptotal Total swap space size at this moment (snapshot).
258 swpfree Available swap space at this moment (snapshot).
260 The output for the flag -s contains information about the frequency of
262 swapping:
263 pagescan/s Number of scanned pages per second due to the fact that
265 free memory drops below a particular threshold.
266 swapin/s The number of memory-pages the system read from the swap-
268 device per second.
269 swapout/s The number of memory-pages the system wrote to the swap-
271 device per second.
272 commitspc The committed virtual memory space i.e. the reserved vir‐
274 tual space for all allocations of private memory space for
275 processes.
276 commitlim The maximum limit for the committed space, which is by
278 default swap size plus 50% of memory size. The kernel only
279 verifies whether the committed space exceeds the limit if
280 strict overcommit handling is configured (vm.overcom‐
281 mit_memory is 2).
282 The output for the flags -l (LVM), -f (MD), and -d (hard disk) contains
284 the following columns per active unit:
285 disk Name.
287 busy Busy-percentage of the unit (i.e. the portion of time that
289 the device was busy handling requests).
290 read/s Number of read-requests issued per second on this unit.
292 KB/read Average number of Kbytes transferred per read-request for
294 this unit.
295 writ/s Number of write-requests issued per second on this unit.
297 KB/writ Average number of Kbytes transferred per write-request for
299 this unit.
300 avque Average number of requests outstanding in the queue during
302 the time that the unit is busy.
303 avserv Average number of milliseconds needed by a request on this
305 unit (seek, latency and data-transfer).
306 The output for the flag -n contains information about activity on NFS
308 mounted filesystems (client):
309 mounted_device
311 Mounted device containing server name and server directory
312 being mounted.
313 physread/s Kilobytes data physically read from the NFS server by pro‐
315 cesses running on the NFS client.
316 KBwrite/s Kilobytes data physically written to the NFS server by pro‐
318 cesses running on the NFS client.
319 When the NFS filesystem was mounted during the interval,
320 the state 'M' is shown.
321 The output for the flag -j contains information about NFS client activ‐
323 ity:
324 rpc/s Number of RPC calls per second issued to NFS server(s).
326 rpcread/s Number of read RPC calls per second issued to NFS
328 server(s).
329 rpcwrite/s Number of write RPC calls per second issued to NFS
331 server(s).
332 retrans/s Number of retransmitted RPC calls per second.
334 autrefresh/s
336 Number of authorization refreshes per second.
337 The output for the flag -J contains information about NFS server activ‐
339 ity:
340 rpc/s Number of RPC calls per second received from NFS client(s).
342 rpcread/s Number of read RPC calls per second received from NFS
344 client(s).
345 rpcwrite/s Number of write RPC calls per second received from NFS
347 client(s).
348 MBcr/s Number of Megabytes per second returned to read requests by
350 clients.
351 MBcw/s Number of Megabytes per second passed in write requests by
353 clients.
354 nettcp/s Number of requests per second handled via TCP.
356 netudp/s Number of requests per second handled via UDP.
358 The output for the flag -i provides information about utilization of
360 network interfaces:
361 interf Name of interface.
363 busy Busy percentage for this interface. If the linespeed of
365 this interface could not be determined (for virtual inter‐
366 faces or in case that atop or atopsar had no root-privi‐
367 leges), a question mark is shown.
368 ipack/s Number of packets received from this interface per second.
370 opack/s Number of packets transmitted to this interface per second.
372 iKbyte/s Number of Kbytes received from this interface per second.
374 oKbyte/s Number of Kbytes transmitted via this interface per second.
376 imbps/s Effective number of megabits received per second.
378 ombps/s Effective number of megabits transmitted per second.
380 maxmbps/s Linespeed as number of megabits per second. If the line‐
382 speed could not be determined (for virtual interfaces or in
383 case that atop or atopsar had no root-privileges), value 0
384 is shown.
385 The linespeed is followed by the indication 'f' (full
386 duplex) or 'h' (half duplex).
387 The output for the flag -I provides information about the failures that
389 were detected for network interfaces:
390 interf Name of interface.
392 ierr/s Number of bad packets received from this interface per sec‐
394 ond.
395 oerr/s Number of times that packet transmission to this interface
397 failed per second.
398 coll/s Number of collisions encountered per second while transmit‐
400 ting packets.
401 idrop/s Number of received packets dropped per second due to lack
403 of buffer-space in the local system.
404 odrop/s Number of transmitted packets dropped per second due to
406 lack of buffer-space in the local system.
407 iframe/s Number of frame alignment-errors encountered per second on
409 received packets.
410 ocarrier/s Number of carrier-errors encountered per second on trans‐
412 mitted packets.
413 The output for the flag -w provides information about the utilization
415 of the IPv4-layer (formal SNMP-names between brackets):
416 inrecv/s Number of IP datagrams received from interfaces per second,
418 including those received in error (ipInReceives).
419 outreq/s Number of IP datagrams that local higher-layer protocols
421 supplied to IP in requests for transmission per second
422 (ipOutRequests).
423 indeliver/s Number of received IP datagrams that have been successfully
425 delivered to higher protocol-layers per second (ipInDeliv‐
426 ers).
427 forward/s Number of received IP datagrams per second for which this
429 entity was not their final IP destination, as a result of
430 which an attempt was made to forward (ipForwDatagrams).
431 reasmok/s Number of IP datagrams successfully reassembled per second
433 (ipReasmOKs).
434 fragcreat/s Number of IP datagram fragments generated per second at
436 this entity (ipFragCreates).
437 The output for the flag -W provides information about the failures that
439 were detected in the IPv4-layer (formal SNMP-names between brackets):
440 in: dsc/s Number of input IP datagrams per second for which no prob‐
442 lems were encountered to prevent their continued processing
443 but that were discarded, e.g. for lack of buffer space
444 (ipInDiscards).
445 in: hder/s Number of input IP datagrams per second discarded due to
447 errors in the IP header (ipInHdrErrors).
448 in: ader/s Number of input IP datagrams per second discarded because
450 the IP address in the destination field was not valid to be
451 received by this entity (ipInAddrErrors).
452 in: unkp/s Number of inbound packets per second that were discarded
454 because of an unknown or unsupported protocol (ipInUnknown‐
455 Protos).
456 in: ratim/s Number of timeout-situations per second while other frag‐
458 ments were expected for successful reassembly (ipReasmTime‐
459 out).
460 in: rfail/s Number of failures detected per second by the IP reassembly
462 algorithm (ipReasmFails).
463 out: dsc/s Number of output IP datagrams per second for which no prob‐
465 lems were encountered to prevent their continued processing
466 but that were discarded, e.g. for lack of buffer space
467 (ipOutDiscards).
468 out: nrt/s Number of IP datagrams per second discarded because no
470 route could be found (ipOutNoRoutes).
471 The output for the flag -y provides information about the general uti‐
473 lization of the ICMPv4-layer and some information per type of ICMP-mes‐
474 sage (formal SNMP-names between brackets):
475 intot/s Number of ICMP messages (any type) received per second at
477 this entity (icmpInMsgs).
478 outtot/s Number of ICMP messages (any type) transmitted per second
480 from this entity (icmpOutMsgs).
481 inecho/s Number of ICMP Echo (request) messages received per second
483 (icmpInEchos).
484 inerep/s Number of ICMP Echo-Reply messages received per second
486 (icmpInEchoReps).
487 otecho/s Number of ICMP Echo (request) messages transmitted per sec‐
489 ond (icmpOutEchos).
490 oterep/s Number of ICMP Echo-Reply messages transmitted per second
492 (icmpOutEchoReps).
493 The output for the flag -Y provides information about other types of
495 ICMPv4-messages (formal SNMP-names between brackets):
496 ierr/s Number of ICMP messages received per second but determined
498 to have ICMP-specific errors (icmpInErrors).
499 isq/s Number of ICMP Source Quench messages received per second
501 (icmpInSrcQuenchs).
502 ird/s Number of ICMP Redirect messages received per second (icmp‐
504 InRedirects).
505 idu/s Number of ICMP Destination Unreachable messages received
507 per second (icmpInDestUnreachs).
508 ite/s Number of ICMP Time Exceeded messages received per second
510 (icmpOutTimeExcds).
511 oerr/s Number of ICMP messages transmitted per second but deter‐
513 mined to have ICMP-specific errors (icmpOutErrors).
514 osq/s Number of ICMP Source Quench messages transmitted per sec‐
516 ond (icmpOutSrcQuenchs).
517 ord/s Number of ICMP Redirect messages transmitted per second
519 (icmpOutRedirects).
520 odu/s Number of ICMP Destination Unreachable messages transmitted
522 per second (icmpOutDestUnreachs).
523 ote/s Number of ICMP Time Exceeded messages transmitted per sec‐
525 ond (icmpOutTimeExcds).
526 The output for the flag -u provides information about the utilization
528 of the UDPv4-layer (formal SNMP-names between brackets):
529 indgram/s Number of UDP datagrams per second delivered to UDP users
531 (udpInDatagrams).
532 outdgram/s Number of UDP datagrams transmitted per second from this
534 entity (udpOutDatagrams).
535 inerr/s Number of received UDP datagrams per second that could not
537 be delivered for reasons other than the lack of an applica‐
538 tion at the destination port (udpInErrors).
539 noport/s Number of received UDP datagrams per second for which there
541 was no application at the destination port (udpNoPorts).
542 The output for the flag -z provides information about the utilization
544 of the IPv6-layer (formal SNMP-names between brackets):
545 inrecv/s Number of input IPv6-datagrams received from interfaces per
547 second, including those received in error (ipv6IfStatsInRe‐
548 ceives).
549 outreq/s Number of IPv6-datagrams per second that local higher-layer
551 protocols supplied to IP in requests for transmission
552 (ipv6IfStatsOutRequests). This counter does not include
553 any forwarded datagrams.
554 inmc/s Number of multicast packets per second that have been
556 received by the interface (ipv6IfStatsInMcastPkts).
557 outmc/s Number of multicast packets per second that have been
559 transmitted to the interface (ipv6IfStatsOutMcastPkts).
560 indeliv/s Number of IP datagrams successfully delivered per second to
562 IPv6 user-protocols, including ICMP (ipv6IfStatsInDeliv‐
563 ers).
564 reasmok/s Number of IPv6 datagrams successfully reassembled per sec‐
566 ond (ipv6IfStatsReasmOKs).
567 fragcre/s Number of IPv6 datagram fragments generated per second at
569 this entity (ipv6IfStatsOutFragCreates).
570 The output for the flag -Z provides information about the failures that
572 were detected in the IPv6-layer (formal SNMP-names between brackets):
573 in: dsc/s Number of input IPv6 datagrams per second for which no
575 problems were encountered to prevent their continued pro‐
576 cessing but that were discarded, e.g. for lack of buffer
577 space (ipv6IfStatsInDiscards).
578 in: hder/s Number of input datagrams per second discarded due to
580 errors in the IPv6 header (ipv6IfStatsInHdrErrors).
581 in: ader/s Number of input datagrams per second discarded because the
583 IPv6 address in the destination field was not valid to be
584 received by this entity (ipv6IfStatsInAddrErrors).
585 in: unkp/s Number of locally-addressed datagrams per second that were
587 discarded because of an unknown or unsupported protocol
588 (ipv6IfStatsInUnknownProtos).
589 in: ratim/s Number of timeout-situations per second while other IPv6
591 fragments were expected for successful reassembly
592 (ipv6ReasmTimeout).
593 in: rfail/s Number of failures detected per second by the IPv6 reassem‐
595 bly-algorithm (ipv6IfStatsReasmFails).
596 out: dsc/s Number of output IPv6 datagrams per second for which no
598 problems were encountered to prevent their continued pro‐
599 cessing but that were discarded, e.g. for lack of buffer
600 space (ipv6IfStatsOutDiscards).
601 out: nrt/s Number of IPv6 datagrams per second discarded because no
603 route could be found (ipv6IfStatsInNoRoutes).
604 The output for the flag -k provides information about the general uti‐
606 lization of the ICMPv6-layer and some information per type of ICMP-mes‐
607 sage (formal SNMP-names between brackets):
608 intot/s Number of ICMPv6 messages (any type) received per second at
610 the interface (ipv6IfIcmpInMsgs).
611 outtot/s Number of ICMPv6 messages (any type) transmitted per second
613 from this entity (ipv6IfIcmpOutMsgs).
614 inerr/s Number of ICMPv6 messages received per second that had
616 ICMP-specific errors, such as bad ICMP checksums, bad
617 length, etc (ipv6IfIcmpInErrors).
618 innsol/s Number of ICMP Neighbor Solicit messages received per sec‐
620 ond (ipv6IfIcmpInNeighborSolicits).
621 innadv/s Number of ICMP Neighbor Advertisement messages received per
623 second (ipv6IfIcmpInNeighborAdvertisements).
624 otnsol/s Number of ICMP Neighbor Solicit messages transmitted per
626 second (ipv6IfIcmpOutNeighborSolicits).
627 otnadv/s Number of ICMP Neighbor Advertisement messages transmitted
629 per second (ipv6IfIcmpOutNeighborAdvertisements).
630 The output for the flag -K provides information about other types of
632 ICMPv6-messages (formal SNMP-names between brackets):
633 iecho/s Number of ICMP Echo (request) messages received per second
635 (ipv6IfIcmpInEchos).
636 ierep/s Number of ICMP Echo-Reply messages received per second
638 (ipv6IfIcmpInEchoReplies).
639 oerep/s Number of ICMP Echo-Reply messages transmitted per second
641 (ipv6IfIcmpOutEchoReplies).
642 idu/s Number of ICMP Destination Unreachable messages received
644 per second (ipv6IfIcmpInDestUnreachs).
645 odu/s Number of ICMP Destination Unreachable messages transmitted
647 per second (ipv6IfIcmpOutDestUnreachs).
648 ird/s Number of ICMP Redirect messages received per second
650 (ipv6IfIcmpInRedirects).
651 ord/s Number of ICMP Redirect messages transmitted per second
653 (ipv6IfIcmpOutRedirect).
654 ite/s Number of ICMP Time Exceeded messages received per second
656 (ipv6IfIcmpInTimeExcds).
657 ote/s Number of ICMP Time Exceeded messages transmitted per sec‐
659 ond (ipv6IfIcmpOutTimeExcds).
660 The output for the flag -U provides information about the utilization
662 of the UDPv6-layer (formal SNMP-names between brackets):
663 indgram/s Number of UDPv6 datagrams per second delivered to UDP users
665 (udpInDatagrams),
666 outdgram/s Number of UDPv6 datagrams transmitted per second from this
668 entity (udpOutDatagrams),
669 inerr/s Number of received UDPv6 datagrams per second that could
671 not be delivered for reasons other than the lack of an
672 application at the destination port (udpInErrors).
673 noport/s Number of received UDPv6 datagrams per second for which
675 there was no application at the destination port (udpNo‐
676 Ports).
677 The output for the flag -t provides information about the utilization
679 of the TCP-layer (formal SNMP-names between brackets):
680 insegs/s Number of received segments per second, including those
682 received in error (tcpInSegs).
683 outsegs/s Number of transmitted segments per second, excluding those
685 containing only retransmitted octets (tcpOutSegs).
686 actopen/s Number of active opens per second that have been supported
688 by this entity (tcpActiveOpens).
689 pasopen/s Number of passive opens per second that have been supported
691 by this entity (tcpPassiveOpens).
692 nowopen Number of connections currently open (snapshot), for which
694 the state is either ESTABLISHED or CLOSE-WAIT (tcpCur‐
695 rEstab).
696 The output for the flag -T provides information about the failures that
698 were detected in the TCP-layer (formal SNMP-names between brackets):
699 inerr/s Number of received segments per second received in error
701 (tcpInErrs).
702 retrans/s Number of retransmitted segments per second (tcpRe‐
704 transSegs).
705 attfail/s Number of failed connection attempts per second that have
707 occurred at this entity (tcpAttemptFails).
708 estabreset/s
710 Number of resets per second that have occurred at this
711 entity (tcpEstabResets).
712 outreset/s Number of transmitted segments per second containing the
714 RST flag (tcpOutRsts).
715 The output for the flag -O provides information about the top-3 of pro‐
717 cesses with the highest processor consumption:
718 pid Process-id (if zero, the process has exited while the pid
720 could not be determined).
721 command The name of the process.
723 cpu% The percentage of cpu-capacity being consumed. This value
725 can exceed 100% for a multithreaded process running on a
726 multiprocessor machine.
727 The output for the flag -G provides information about the top-3 of pro‐
729 cesses with the highest memory consumption:
730 pid Process-id (if zero, the process has exited while the pid
732 could not be determined).
733 command The name of the process.
735 mem% The percentage of resident memory-utilization by this
737 process.
738 The output for the flag -D provides information about the top-3 of pro‐
740 cesses that issue the most read and write accesses to disk:
741 pid Process-id (if zero, the process has exited while the pid
743 could not be determined).
744 command The name of the process.
746 dsk% The percentage of read and write accesses related to the
748 total number of read and write accesses issued on disk by
749 all processes, so a high percentage does not imply a high
750 disk load on system level.
751 The output for the flag -N provides information about the top-3 of pro‐
753 cesses that issue the most socket transfers for IPv4/IPv6:
754 pid Process-id (if zero, the process has exited while the pid
756 could not be determined).
757 command The name of the process.
759 net% The percentage of socket transfers related to the total
761 number of transfers issued by all processes, so a high per‐
762 centage does not imply a high network load on system level.
763
765 To see today's cpu-activity so far (supposed that atop is logging in
766 the background):
767 atopsar
769 To see the memory occupation for June 5, 2012 between 10:00 and 12:30
771 (supposed that atop has been logging daily in the background):
772 atopsar -m -r /var/log/atop_20120605 -b 10:00 -e 12:30
774 or
776 atopsar -m -r 20120605 -b 10:00 -e 12:30
778 or, suppose it is June 8, 2012 at this moment
780 atopsar -m -r yyy -b 10:00 -e 12:30
782 Write a logfile with atop to record the system behaviour for 30 minutes
784 (30 samples of one minute) and produce all available reports after‐
785 wards:
786 atop -w /tmp/atoplog 60 30
788 atopsar -A -r /tmp/atoplog
790 To watch TCP activity evolve for ten minutes (10 samples with sixty
792 seconds interval):
793 atopsar -t 60 10
795 To watch the header-lines ('_' as last character) of all reports with
797 only the detail-lines showing critical resource consumption (marker '*'
798 or '+' as last character):
799 atopsar -AM | grep '[_*+]$'
801
803 /etc/atoprc
804 Configuration file containing system-wide default values (mainly
805 flags). See related man-page.
806 ~/.atoprc
808 Configuration file containing personal default values (mainly
809 flags). See related man-page.
810 /var/log/atop/atop_YYYYMMDD
812 Daily data file, where YYYYMMDD are digits representing the date.
813
815 atop(1), atoprc(5), atopacctd(8), netatop(4), netatopd(8)
816 http://www.atoptool.nl
817
819 Gerlof Langeveld (gerlof.langeveld@atoptool.nl)
820Linux March 2017 ATOPSAR(1)