To move back to the previous snapshot, press the ' T' (uppercase ' t') key. To move forward to the next snapshot, press the ‘ t’ key on the keyboard. In the preceding output example, the first recorded snapshot was at 2 17:03:44. PRC | sys 6.51s | user 7.85s | #proc 103 | #tslpi 81 | #tslpu 0 | #zombie 0 | #exit 0 |ĬPU | sys 0% | user 3% | irq 0% | idle 197% | wait 0% | ipc notavail | curscal ?% |Ĭpu | sys 0% | user 1% | irq 0% | idle 98% | cpu000 w 0% | ipc notavail | curscal ?% |Ĭpu | sys 0% | user 1% | irq 0% | idle 98% | cpu001 w 0% | ipc notavail | curscal ?% | The command and log file are shown in the following example: atop -r /var/log/atop/atop_20210902ĪTOP - ip-172-20-139-91 2 17:03:44 - 3h33m7s elapsed To access the log file, run the command atop -r atologfilepath. For example, ' atop_20210902' is the recording for September 2, 2021. These files are named in the following format ' atop_ccyymmdd'. The data is stored in log files in /var/log/atop. Red Hat-based systems $sudo sed 's/600/60/' /etc/atop/atop.daily -iĭebian-based systems $ sudo sed 's/600/60/' /etc/default/atop -iĪfter running the preceding command, atop logs all activities within 60-second internals. To change the atop tool's configuration so that activities are logged in 60-second intervals, run the following command: The atop tool logs all activity in 600-second intervals by default. Red Hat-based systems $ sudo yum install atopĭebian-based systems $ sudo apt install atop Install the atop tool by running the following commands: The atop tool is included in official repositories for most Linux distributions. Because of this continuous logging, if issues reoccur, you have historical data to analyze. This tool logs all relevant system information continuously. The atop tool reports the activity of all processes, even if those processes have finished during the specified interval. The iostat, vmstat, and mpstat commands.The following are resources you can use to analyze and monitor your Lightsail instance's resources from the command line: This also allows for a granular view of which processes are using the most CPU, memory, disk I/O, or network.

Using common tools you can monitor resources such as CPU, memory, disk I/O, and network usage on Lightsail instances in real time from the command line.Īnalyzing and monitoring Lightsail instance resource usage from the command line provides real-time system insight.

There are several factors, including high resource utilization, that affect services running on Lightsail instances.

Htop network usage