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 [YYYYMMDD]hhmm ]
10 [-e [YYYYMMDD]hhmm ]
11 atopsar [-flags...] interval [ samples ]
12
14 The program atopsar can be used to report statistics on system level.
15 In the first synopsis line (no sampling interval specified), atopsar
17 extracts data from a raw logfile that has been recorded previously by
18 the program atop (option -w of the atop program).
19 You can specify the name of the logfile with the -r option of the atop‐
20 sar program. When a daily logfile of atop is used, named
21 /var/log/atop/atop_YYYYMMDD (where YYYYMMDD reflects the date), the
22 required date of the form YYYYMMDD can be specified with the -r option
23 instead of the filename, or the symbolic name 'y' can be used for yes‐
24 terday's daily logfile (this can be repeated so 'yyyy' indicates the
25 logfile of four days ago), or the filename '-' can be used to read raw
26 data from stdin. If the -r option is not specified at all, today's
27 daily logfile is used by default.
28 The starting and ending times of the report can be defined using the
29 options -b and -e followed by a time argument of the form [YYYYM‐
30 MDD]hhmm.
31 In the second synopsis line, atopsar reads actual activity counters
33 from the kernel with the specified interval (in seconds) and the speci‐
34 fied number of samples (optionally). When atopsar is activated in this
35 way it immediately sends the output for every requested report to stan‐
36 dard output. If only one type of report is requested, the header is
37 printed once and after every interval seconds the statistical counters
38 are shown for that period. If several reports are requested, a header
39 is printed per sample followed by the statistical counters for that
40 period.
41 Some generic flags can be specified to influence the behaviour of the
43 atopsar program:
44 -S By default the timestamp at the beginning of a line is suppressed
46 if more lines are shown for one interval. With this flag a time‐
47 stamp is given for every output-line (easier for post-processing).
48 -a By default certain resources as disks and network interfaces are
50 only shown when they were active during the interval. With this
51 flag all resources of a given type are shown, even if they were
52 inactive during the interval.
53 -x By default atopsar only uses colors if output is directed to a
55 terminal (window). These colors might indicate that a critical
56 occupation percentage has been reached (red) or has been almost
57 reached (cyan) for a particular resource. See the man-page of
58 atop for a detailed description of this feature (section COLORS).
59 With the flag -x the use of colors is suppressed unconditionally.
60 -C By default atopsar only uses colors if output is directed to a
62 terminal (window). These colors might indicate that a critical
63 occupation percentage has been reached (red) or has been almost
64 reached (cyan) for a particular resource. See the man-page of
65 atop for a detailed description of this feature (section COLORS).
66 With the flag -C colors will always be used, even if output is not
67 directed to a terminal.
68 -M Use markers at the end of a line to indicate that a critical occu‐
70 pation percentage has been reached ('*') or has been almost
71 reached ('+') for particular resources. The marker '*' is similar
72 to the color red and the marker '+' to the color cyan. See the
73 man-page of atop for a detailed description of these colors (sec‐
74 tion COLORS).
75 -H Repeat the header line within a report for every N detail lines.
77 The value of N is determined dynamically in case of output to a
78 tty/window (depending on the number of lines); for output to a
79 file or pipe this value is 23.
80 -R Summarize cnt samples into one sample. When the logfile contains
82 e.g. samples of 10 minutes, the use of the flag '-R 6' shows a
83 report with one sample for every hour.
84 Other flags are used to define which reports are required:
86 -A Show all possible reports.
88 -c Report about CPU utilization (in total and per cpu).
90 -g Report about GPU utilization (per GPU).
92 -p Report about processor-related matters, like load-averages and
94 hardware interrupts.
95 -P Report about processes.
97 -m Current memory- and swap-occupation.
99 -s Report about paging- and swapping-activity, and overcommitment.
101 -B Report about Pressure Stall Information (PSI).
103 -l Report about utilization of logical volumes.
105 -f Report about utilization of multiple devices.
107 -d Report about utilization of disks.
109 -n Report about NFS mounted filesystems on NFS client.
111 -j Report about NFS client activity.
113 -J Report about NFS server activity.
115 -i Report about the network interfaces.
117 -I Report about errors for network-interfaces.
119 -w Report about IP version 4 network traffic.
121 -W Report about errors for IP version 4 traffic.
123 -y General report about ICMP version 4 layer activity.
125 -Y Per-type report about ICMP version 4 layer activity.
127 -u Report about UDP version 4 network traffic.
129 -z Report about IP version 6 network traffic.
131 -Z Report about errors for IP version 6 traffic.
133 -k General report about ICMP version 6 layer activity.
135 -K Per-type report about ICMP version 6 layer activity.
137 -U Report about UDP version 6 network traffic.
139 -t Report about TCP network traffic.
141 -T Report about errors for TCP-traffic.
143 -h Report about Infiniband utilization.
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 -g contains the following columns per GPU:
203 busaddr GPU number and bus-ID (separated by '/').
205 gpubusy GPU busy percentage during interval.
207 membusy GPU memory busy percentage during interval, i.e. time to
209 issue read and write accesses on memory.
210 memocc Percentage of memory occupation at this moment.
212 memtot Total memory available.
214 memuse Used GPU memory at this moment.
216 gputype Type of GPU.
218 The output for the flag -p contains the following values:
220 pswch/s Number of process switches (also called context switches)
222 per second on this cpu. A process switch occurs at the
223 moment that an active thread (i.e. the thread using a cpu)
224 enters a wait state or has used its time slice completely;
225 another thread will then be chosen to use the cpu.
226 devintr/s Number of hardware interrupts handled per second on this
228 cpu.
229 clones/s The number of new threads started per second.
231 loadavg1 Load average reflecting the average number of threads in
233 the runqueue or in non-interruptible wait state (usually
234 waiting for disk or tape I/O) during the last minute.
235 loadavg5 Load average reflecting the average number of threads in
237 the runqueue or in non-interruptible wait state (usually
238 waiting for disk or tape I/O) during the last 5 minutes.
239 loadavg15 Load average reflecting the average number of threads in
241 the runqueue or in non-interruptible wait state (usually
242 waiting for disk or tape I/O) during the last 15 minutes.
243 The output for the flag -P contains information about the processes and
245 threads:
246 clones/s The number of new threads started per second.
248 pexit/s
250 curproc Total number of processes present in the system.
252 curzomb Number of zombie processes present in the system.
254 thrrun Total number of threads present in the system in state
256 'running'.
257 thrslpi Total number of threads present in the system in state
259 'interruptible sleeping'.
260 thrslpu Total number of threads present in the system in state
262 'uninterruptible sleeping'.
263 The output for the flag -m contains information about the memory- and
265 swap-utilization:
266 memtotal Total usable main memory size.
268 memfree Available main memory size at this moment (snapshot).
270 buffers Main memory used at this moment to cache metadata-blocks
272 (snapshot).
273 cached Main memory used at this moment to cache data-blocks (snap‐
275 shot).
276 dirty Amount of memory in the page cache that still has to be
278 flushed to disk at this moment (snapshot).
279 slabmem Main memory used at this moment for dynamically allocated
281 memory by the kernel (snapshot).
282 swptotal Total swap space size at this moment (snapshot).
284 swpfree Available swap space at this moment (snapshot).
286 The output for the flag -s contains information about the frequency of
288 swapping:
289 pagescan/s Number of scanned pages per second due to the fact that
291 free memory drops below a particular threshold.
292 swapin/s The number of memory-pages the system read from the swap-
294 device per second.
295 swapout/s The number of memory-pages the system wrote to the swap-
297 device per second.
298 commitspc The committed virtual memory space i.e. the reserved vir‐
300 tual space for all allocations of private memory space for
301 processes.
302 commitlim The maximum limit for the committed space, which is by
304 default swap size plus 50% of memory size. The kernel only
305 verifies whether the committed space exceeds the limit if
306 strict overcommit handling is configured (vm.overcom‐
307 mit_memory is 2).
308 The output for the flag -B contains the Pressure Stall Information
310 (PSI):
311 cpusome Average pressure percentage during the interval for the
313 category 'CPU some'.
314 memsome Average pressure percentage during the interval for the
316 category 'memory some'.
317 memfull Average pressure percentage during the interval for the
319 category 'memory full'.
320 iosome Average pressure percentage during the interval for the
322 category 'I/O some'.
323 iofull Average pressure percentage during the interval for the
325 category 'I/O full'.
326 The output for the flags -l (LVM), -f (MD), and -d (hard disk) contains
328 the following columns per active unit:
329 disk Name.
331 busy Busy-percentage of the unit (i.e. the portion of time that
333 the device was busy handling requests).
334 read/s Number of read-requests issued per second on this unit.
336 KB/read Average number of Kbytes transferred per read-request for
338 this unit.
339 writ/s Number of write-requests issued per second on this unit.
341 KB/writ Average number of Kbytes transferred per write-request for
343 this unit.
344 avque Average number of requests outstanding in the queue during
346 the time that the unit is busy.
347 avserv Average number of milliseconds needed by a request on this
349 unit (seek, latency and data-transfer).
350 The output for the flag -n contains information about activity on NFS
352 mounted filesystems (client):
353 mounted_device
355 Mounted device containing server name and server directory
356 being mounted.
357 physread/s Kilobytes data physically read from the NFS server by pro‐
359 cesses running on the NFS client.
360 KBwrite/s Kilobytes data physically written to the NFS server by pro‐
362 cesses running on the NFS client.
363 When the NFS filesystem was mounted during the interval,
364 the state 'M' is shown.
365 The output for the flag -j contains information about NFS client activ‐
367 ity:
368 rpc/s Number of RPC calls per second issued to NFS server(s).
370 rpcread/s Number of read RPC calls per second issued to NFS
372 server(s).
373 rpcwrite/s Number of write RPC calls per second issued to NFS
375 server(s).
376 retrans/s Number of retransmitted RPC calls per second.
378 autrefresh/s
380 Number of authorization refreshes per second.
381 The output for the flag -J contains information about NFS server activ‐
383 ity:
384 rpc/s Number of RPC calls per second received from NFS client(s).
386 rpcread/s Number of read RPC calls per second received from NFS
388 client(s).
389 rpcwrite/s Number of write RPC calls per second received from NFS
391 client(s).
392 MBcr/s Number of Megabytes per second returned to read requests by
394 clients.
395 MBcw/s Number of Megabytes per second passed in write requests by
397 clients.
398 nettcp/s Number of requests per second handled via TCP.
400 netudp/s Number of requests per second handled via UDP.
402 The output for the flag -i provides information about utilization of
404 network interfaces:
405 interf Name of interface.
407 busy Busy percentage for this interface. If the linespeed of
409 this interface could not be determined (for virtual inter‐
410 faces or in case that atop or atopsar had no root-privi‐
411 leges), a question mark is shown.
412 ipack/s Number of packets received from this interface per second.
414 opack/s Number of packets transmitted to this interface per second.
416 iKbyte/s Number of Kbytes received from this interface per second.
418 oKbyte/s Number of Kbytes transmitted via this interface per second.
420 imbps/s Effective number of megabits received per second.
422 ombps/s Effective number of megabits transmitted per second.
424 maxmbps/s Linespeed as number of megabits per second. If the line‐
426 speed could not be determined (for virtual interfaces or in
427 case that atop or atopsar had no root-privileges), value 0
428 is shown.
429 The linespeed is followed by the indication 'f' (full
430 duplex) or 'h' (half duplex).
431 The output for the flag -I provides information about the failures that
433 were detected for network interfaces:
434 interf Name of interface.
436 ierr/s Number of bad packets received from this interface per sec‐
438 ond.
439 oerr/s Number of times that packet transmission to this interface
441 failed per second.
442 coll/s Number of collisions encountered per second while transmit‐
444 ting packets.
445 idrop/s Number of received packets dropped per second due to lack
447 of buffer-space in the local system.
448 odrop/s Number of transmitted packets dropped per second due to
450 lack of buffer-space in the local system.
451 iframe/s Number of frame alignment-errors encountered per second on
453 received packets.
454 ocarrier/s Number of carrier-errors encountered per second on trans‐
456 mitted packets.
457 The output for the flag -w provides information about the utilization
459 of the IPv4-layer (formal SNMP-names between brackets):
460 inrecv/s Number of IP datagrams received from interfaces per second,
462 including those received in error (ipInReceives).
463 outreq/s Number of IP datagrams that local higher-layer protocols
465 supplied to IP in requests for transmission per second
466 (ipOutRequests).
467 indeliver/s Number of received IP datagrams that have been successfully
469 delivered to higher protocol-layers per second (ipInDeliv‐
470 ers).
471 forward/s Number of received IP datagrams per second for which this
473 entity was not their final IP destination, as a result of
474 which an attempt was made to forward (ipForwDatagrams).
475 reasmok/s Number of IP datagrams successfully reassembled per second
477 (ipReasmOKs).
478 fragcreat/s Number of IP datagram fragments generated per second at
480 this entity (ipFragCreates).
481 The output for the flag -W provides information about the failures that
483 were detected in the IPv4-layer (formal SNMP-names between brackets):
484 in: dsc/s Number of input IP datagrams per second for which no prob‐
486 lems were encountered to prevent their continued processing
487 but that were discarded, e.g. for lack of buffer space
488 (ipInDiscards).
489 in: hder/s Number of input IP datagrams per second discarded due to
491 errors in the IP header (ipInHdrErrors).
492 in: ader/s Number of input IP datagrams per second discarded because
494 the IP address in the destination field was not valid to be
495 received by this entity (ipInAddrErrors).
496 in: unkp/s Number of inbound packets per second that were discarded
498 because of an unknown or unsupported protocol (ipInUnknown‐
499 Protos).
500 in: ratim/s Number of timeout-situations per second while other frag‐
502 ments were expected for successful reassembly (ipReasmTime‐
503 out).
504 in: rfail/s Number of failures detected per second by the IP reassembly
506 algorithm (ipReasmFails).
507 out: dsc/s Number of output IP datagrams per second for which no prob‐
509 lems were encountered to prevent their continued processing
510 but that were discarded, e.g. for lack of buffer space
511 (ipOutDiscards).
512 out: nrt/s Number of IP datagrams per second discarded because no
514 route could be found (ipOutNoRoutes).
515 The output for the flag -y provides information about the general uti‐
517 lization of the ICMPv4-layer and some information per type of ICMP-mes‐
518 sage (formal SNMP-names between brackets):
519 intot/s Number of ICMP messages (any type) received per second at
521 this entity (icmpInMsgs).
522 outtot/s Number of ICMP messages (any type) transmitted per second
524 from this entity (icmpOutMsgs).
525 inecho/s Number of ICMP Echo (request) messages received per second
527 (icmpInEchos).
528 inerep/s Number of ICMP Echo-Reply messages received per second
530 (icmpInEchoReps).
531 otecho/s Number of ICMP Echo (request) messages transmitted per sec‐
533 ond (icmpOutEchos).
534 oterep/s Number of ICMP Echo-Reply messages transmitted per second
536 (icmpOutEchoReps).
537 The output for the flag -Y provides information about other types of
539 ICMPv4-messages (formal SNMP-names between brackets):
540 ierr/s Number of ICMP messages received per second but determined
542 to have ICMP-specific errors (icmpInErrors).
543 isq/s Number of ICMP Source Quench messages received per second
545 (icmpInSrcQuenchs).
546 ird/s Number of ICMP Redirect messages received per second (icmp‐
548 InRedirects).
549 idu/s Number of ICMP Destination Unreachable messages received
551 per second (icmpInDestUnreachs).
552 ite/s Number of ICMP Time Exceeded messages received per second
554 (icmpOutTimeExcds).
555 oerr/s Number of ICMP messages transmitted per second but deter‐
557 mined to have ICMP-specific errors (icmpOutErrors).
558 osq/s Number of ICMP Source Quench messages transmitted per sec‐
560 ond (icmpOutSrcQuenchs).
561 ord/s Number of ICMP Redirect messages transmitted per second
563 (icmpOutRedirects).
564 odu/s Number of ICMP Destination Unreachable messages transmitted
566 per second (icmpOutDestUnreachs).
567 ote/s Number of ICMP Time Exceeded messages transmitted per sec‐
569 ond (icmpOutTimeExcds).
570 The output for the flag -u provides information about the utilization
572 of the UDPv4-layer (formal SNMP-names between brackets):
573 indgram/s Number of UDP datagrams per second delivered to UDP users
575 (udpInDatagrams).
576 outdgram/s Number of UDP datagrams transmitted per second from this
578 entity (udpOutDatagrams).
579 inerr/s Number of received UDP datagrams per second that could not
581 be delivered for reasons other than the lack of an applica‐
582 tion at the destination port (udpInErrors).
583 noport/s Number of received UDP datagrams per second for which there
585 was no application at the destination port (udpNoPorts).
586 The output for the flag -z provides information about the utilization
588 of the IPv6-layer (formal SNMP-names between brackets):
589 inrecv/s Number of input IPv6-datagrams received from interfaces per
591 second, including those received in error (ipv6IfStatsInRe‐
592 ceives).
593 outreq/s Number of IPv6-datagrams per second that local higher-layer
595 protocols supplied to IP in requests for transmission
596 (ipv6IfStatsOutRequests). This counter does not include
597 any forwarded datagrams.
598 inmc/s Number of multicast packets per second that have been
600 received by the interface (ipv6IfStatsInMcastPkts).
601 outmc/s Number of multicast packets per second that have been
603 transmitted to the interface (ipv6IfStatsOutMcastPkts).
604 indeliv/s Number of IP datagrams successfully delivered per second to
606 IPv6 user-protocols, including ICMP (ipv6IfStatsInDeliv‐
607 ers).
608 reasmok/s Number of IPv6 datagrams successfully reassembled per sec‐
610 ond (ipv6IfStatsReasmOKs).
611 fragcre/s Number of IPv6 datagram fragments generated per second at
613 this entity (ipv6IfStatsOutFragCreates).
614 The output for the flag -Z provides information about the failures that
616 were detected in the IPv6-layer (formal SNMP-names between brackets):
617 in: dsc/s Number of input IPv6 datagrams per second for which no
619 problems were encountered to prevent their continued pro‐
620 cessing but that were discarded, e.g. for lack of buffer
621 space (ipv6IfStatsInDiscards).
622 in: hder/s Number of input datagrams per second discarded due to
624 errors in the IPv6 header (ipv6IfStatsInHdrErrors).
625 in: ader/s Number of input datagrams per second discarded because the
627 IPv6 address in the destination field was not valid to be
628 received by this entity (ipv6IfStatsInAddrErrors).
629 in: unkp/s Number of locally-addressed datagrams per second that were
631 discarded because of an unknown or unsupported protocol
632 (ipv6IfStatsInUnknownProtos).
633 in: ratim/s Number of timeout-situations per second while other IPv6
635 fragments were expected for successful reassembly
636 (ipv6ReasmTimeout).
637 in: rfail/s Number of failures detected per second by the IPv6 reassem‐
639 bly-algorithm (ipv6IfStatsReasmFails).
640 out: dsc/s Number of output IPv6 datagrams per second for which no
642 problems were encountered to prevent their continued pro‐
643 cessing but that were discarded, e.g. for lack of buffer
644 space (ipv6IfStatsOutDiscards).
645 out: nrt/s Number of IPv6 datagrams per second discarded because no
647 route could be found (ipv6IfStatsInNoRoutes).
648 The output for the flag -k provides information about the general uti‐
650 lization of the ICMPv6-layer and some information per type of ICMP-mes‐
651 sage (formal SNMP-names between brackets):
652 intot/s Number of ICMPv6 messages (any type) received per second at
654 the interface (ipv6IfIcmpInMsgs).
655 outtot/s Number of ICMPv6 messages (any type) transmitted per second
657 from this entity (ipv6IfIcmpOutMsgs).
658 inerr/s Number of ICMPv6 messages received per second that had
660 ICMP-specific errors, such as bad ICMP checksums, bad
661 length, etc (ipv6IfIcmpInErrors).
662 innsol/s Number of ICMP Neighbor Solicit messages received per sec‐
664 ond (ipv6IfIcmpInNeighborSolicits).
665 innadv/s Number of ICMP Neighbor Advertisement messages received per
667 second (ipv6IfIcmpInNeighborAdvertisements).
668 otnsol/s Number of ICMP Neighbor Solicit messages transmitted per
670 second (ipv6IfIcmpOutNeighborSolicits).
671 otnadv/s Number of ICMP Neighbor Advertisement messages transmitted
673 per second (ipv6IfIcmpOutNeighborAdvertisements).
674 The output for the flag -K provides information about other types of
676 ICMPv6-messages (formal SNMP-names between brackets):
677 iecho/s Number of ICMP Echo (request) messages received per second
679 (ipv6IfIcmpInEchos).
680 ierep/s Number of ICMP Echo-Reply messages received per second
682 (ipv6IfIcmpInEchoReplies).
683 oerep/s Number of ICMP Echo-Reply messages transmitted per second
685 (ipv6IfIcmpOutEchoReplies).
686 idu/s Number of ICMP Destination Unreachable messages received
688 per second (ipv6IfIcmpInDestUnreachs).
689 odu/s Number of ICMP Destination Unreachable messages transmitted
691 per second (ipv6IfIcmpOutDestUnreachs).
692 ird/s Number of ICMP Redirect messages received per second
694 (ipv6IfIcmpInRedirects).
695 ord/s Number of ICMP Redirect messages transmitted per second
697 (ipv6IfIcmpOutRedirect).
698 ite/s Number of ICMP Time Exceeded messages received per second
700 (ipv6IfIcmpInTimeExcds).
701 ote/s Number of ICMP Time Exceeded messages transmitted per sec‐
703 ond (ipv6IfIcmpOutTimeExcds).
704 The output for the flag -U provides information about the utilization
706 of the UDPv6-layer (formal SNMP-names between brackets):
707 indgram/s Number of UDPv6 datagrams per second delivered to UDP users
709 (udpInDatagrams),
710 outdgram/s Number of UDPv6 datagrams transmitted per second from this
712 entity (udpOutDatagrams),
713 inerr/s Number of received UDPv6 datagrams per second that could
715 not be delivered for reasons other than the lack of an
716 application at the destination port (udpInErrors).
717 noport/s Number of received UDPv6 datagrams per second for which
719 there was no application at the destination port (udpNo‐
720 Ports).
721 The output for the flag -t provides information about the utilization
723 of the TCP-layer (formal SNMP-names between brackets):
724 insegs/s Number of received segments per second, including those
726 received in error (tcpInSegs).
727 outsegs/s Number of transmitted segments per second, excluding those
729 containing only retransmitted octets (tcpOutSegs).
730 actopen/s Number of active opens per second that have been supported
732 by this entity (tcpActiveOpens).
733 pasopen/s Number of passive opens per second that have been supported
735 by this entity (tcpPassiveOpens).
736 nowopen Number of connections currently open (snapshot), for which
738 the state is either ESTABLISHED or CLOSE-WAIT (tcpCur‐
739 rEstab).
740 The output for the flag -T provides information about the failures that
742 were detected in the TCP-layer (formal SNMP-names between brackets):
743 inerr/s Number of received segments per second received in error
745 (tcpInErrs).
746 retrans/s Number of retransmitted segments per second (tcpRe‐
748 transSegs).
749 attfail/s Number of failed connection attempts per second that have
751 occurred at this entity (tcpAttemptFails).
752 estabreset/s
754 Number of resets per second that have occurred at this
755 entity (tcpEstabResets).
756 outreset/s Number of transmitted segments per second containing the
758 RST flag (tcpOutRsts).
759 The output for the flag -h provides information about utilization of
761 Infiniband ports:
762 controller Name of controller.
764 port Controller port.
766 busy Busy percentage for this port.
768 ipack/s Number of packets received from this port per second.
770 opack/s Number of packets transmitted to this port per second.
772 igbps/s Effective number of gigabits received per second.
774 ogbps/s Effective number of gigabits transmitted per second.
776 maxgbps/s Maximum rate as number of gigabits per second.
778 lanes Number of lanes.
780 The output for the flag -O provides information about the top-3 of pro‐
782 cesses with the highest processor consumption:
783 pid Process-id (if zero, the process has exited while the pid
785 could not be determined).
786 command The name of the process.
788 cpu% The percentage of cpu-capacity being consumed. This value
790 can exceed 100% for a multithreaded process running on a
791 multiprocessor machine.
792 The output for the flag -G provides information about the top-3 of pro‐
794 cesses with the highest memory consumption:
795 pid Process-id (if zero, the process has exited while the pid
797 could not be determined).
798 command The name of the process.
800 mem% The percentage of resident memory-utilization by this
802 process.
803 The output for the flag -D provides information about the top-3 of pro‐
805 cesses that issue the most read and write accesses to disk:
806 pid Process-id (if zero, the process has exited while the pid
808 could not be determined).
809 command The name of the process.
811 dsk% The percentage of read and write accesses related to the
813 total number of read and write accesses issued on disk by
814 all processes, so a high percentage does not imply a high
815 disk load on system level.
816 The output for the flag -N provides information about the top-3 of pro‐
818 cesses that issue the most socket transfers for IPv4/IPv6:
819 pid Process-id (if zero, the process has exited while the pid
821 could not be determined).
822 command The name of the process.
824 net% The percentage of socket transfers related to the total
826 number of transfers issued by all processes, so a high per‐
827 centage does not imply a high network load on system level.
828
830 To see today's cpu-activity so far (supposed that atop is logging in
831 the background):
832 atopsar
834 To see the memory occupation for June 5, 2018 between 10:00 and 12:30
836 (supposed that atop has been logging daily in the background):
837 atopsar -m -r /var/log/atop_20180605 -b 10:00 -e 12:30
839 or
841 atopsar -m -r 20180605 -b 10:00 -e 12:30
843 or, suppose it is June 8, 2018 at this moment
845 atopsar -m -r yyy -b 10:00 -e 12:30
847 Write a logfile with atop to record the system behaviour for 30 minutes
849 (30 samples of one minute) and produce all available reports after‐
850 wards:
851 atop -w /tmp/atoplog 60 30
853 atopsar -A -r /tmp/atoplog
855 To watch TCP activity evolve for ten minutes (10 samples with sixty
857 seconds interval):
858 atopsar -t 60 10
860 To watch the header-lines ('_' as last character) of all reports with
862 only the detail-lines showing critical resource consumption (marker '*'
863 or '+' as last character):
864 atopsar -AM | grep '[_*+]$'
866
868 /etc/atoprc
869 Configuration file containing system-wide default values (mainly
870 flags). See related man-page.
871 ~/.atoprc
873 Configuration file containing personal default values (mainly
874 flags). See related man-page.
875 /var/log/atop/atop_YYYYMMDD
877 Daily data file, where YYYYMMDD are digits representing the date.
878
880 atop(1), atopconvert(1), atopcat(1), atoprc(5), atopacctd(8),
881 netatop(4), netatopd(8)
882 https://www.atoptool.nl
883
885 Gerlof Langeveld (gerlof.langeveld@atoptool.nl)
886Linux December 2020 ATOPSAR(1)