Linux : Mastering Linux System Monitoring Commands: A Practical Guide

 



INTRODUCTION:

In Linux system administration, the command line is your best friend. When it comes to monitoring and managing your Linux systems, a set of command-line tools can provide valuable insights into system performance, resource usage, and potential issues.

 In this blog, we'll explore a curated list of powerful Linux system monitoring commands that every sysadmin and Linux should have in their toolkit.


Table of Contents


Monitoring System Resources:


#top : Real-time view of system processes and resource usage.

#htop : Enhanced and interactive version of top.

#free -m : Display information about system memory usage.

#df -kh : Displays the system storage.

#du : Analyzing disk space usage of any file/directory.


CPU Performance Monitoring:


#ps -aux : Viewing information about active processes.

#mpstat : Monitoring CPU usage statistics.

#pidstat : Detailed statistics about processes and their resource usage.

#top : Real-time view of system processes and resource usage.

#htop : Enhanced and interactive version of top.


Memory Usage Commands:


#free -m : Display information about system memory usage.

#vmstat : Display virtual memory statistics.

#pmap : Mapping memory usage of a process.


Disk I/O Monitoring:


#iostat : Monitoring input/output statistics for block devices.

#iotop : Displaying I/O usage by processes.


Network Monitoring Commands:


#ifconfig : Displaying IP of the machine

#netstat : Viewing network connections, routing tables, and interface statistics.

#iftop : Displaying real-time bandwidth usage.

#nload : Monitoring incoming and outgoing traffic.

#ping : To check the Network connectivity with the destination server/domain/IP.

#telnet : To check the Port Connectivity and establish the connection with the destination


System Information Commands:


#uname : Displaying system information.

#lsb_release : Showing Linux Standard Base information.

#hostnamectl : Querying and changing system hostname and related settings.


Process Management Commands:


#kill : Terminating process by PID.

#pkill : Terminating processes by process names.

#jobs: To display the running jobs with their JobID.

#bg : to run process in background.

#fg : To run process in foreground.

#renice : Adjusting the priority of running processes.

#nice : Launching processes with modified scheduling priority.


Log Analysis Commands :


#tail and #head : Displaying the end or beginning of a file.

#grep : Searching for patterns in log files.

#journalctl : Querying and displaying messages from the journal.


Security Monitoring Commands:


#lsof : Listing open files and processes.

#ss : Displaying socket statistics.

#tcpdump : Capturing and analyzing network traffic.



Conclusion:

Armed with these Linux system monitoring commands, you'll have the tools needed to efficiently manage and troubleshoot your Linux systems. Whether you're a seasoned administrator or just getting started, mastering these commands will empower you to keep your systems running smoothly and proactively address any issues that may arise. Happy command-lining!


====================================================================

                        Thank you,check out more blogs for such information !!

                                                                            For any queries,contact shubhammore07007@gmail.com


 

Comments

Post a Comment

Popular posts from this blog

Nginx : Setting Up Nginx with Load Balancing

Image
This guide explains how to configure Nginx as a load balancer for multiple backend applications running on different ports. The setup includes three application servers running on ports 8001, 8002, and 8003, with Nginx balancing requests among them.   Nginx Configuration Details Individual Server Blocks Each backend application is configured as an independent Nginx server block: Server 1 Configuration ( server1.conf ) [root@server1 conf.d]# cat /etc/nginx/conf.d/server1.conf | grep -v "#"   server { listen 8001; server_tokens off; server_name _; client_max_body_size 35M; charset utf-8; large_client_header_buffers 4 16k; root /usr/share/nginx/server1; index index.html index.php index.cgi; access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; } Server 2 Configuration ( server2.conf ) [root@server1 conf.d]# cat /etc/nginx/conf.d/server2.conf | grep -v "#"     server { listen 8002; server_tokens off;...
Read more

Nginx : Virtual hosting using Location directives

Image
This setup demonstrates a virtual container-based environment in Nginx where multiple locations are configured under a single server block, rather than a load-balancing mechanism. Each location serves a different application based on its respective directory structure. Nginx Configuration Server Configuration server { listen 80; server_tokens off; server_name _; client_max_body_size 35M; charset utf-8; large_client_header_buffers 4 16k; root /usr/share/nginx/server1; index index.html index.php index.cgi; access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; location /server2 { root /usr/share/nginx/; index index.html index.php index.cgi; access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; } location /server3 { root /usr/share/nginx/; index index.html index.php index.cgi; access_log /var/log/nginx/access.log; error_log /...
Read more

Terraform project with AWS to build infra within seconds! (Web Ec2 with eIP)

Image
1. Introduction: What is Terraform? Terraform is an open-source Infrastructure as Code (IaC) tool created by HashiCorp. It lets you define, provision, and manage cloud infrastructure using declarative configuration files . Instead of manually creating AWS resources in the console, you write code that describes what you want, and Terraform takes care of creating or updating it. Why use it with AWS? a) Infrastructure as Code (IaC) You can define AWS resources (EC2, VPC, S3, IAM, etc.) in .tf files. These configurations can be version-controlled in Git. b) Multi-Cloud Support Although AWS has its own tool (CloudFormation), Terraform works with AWS + Azure + GCP + on-prem at the same time. c) Reusability & Automation You can reuse Terraform modules to deploy the same AWS setup in different environments (dev, test, prod). d) State Management Terraform keeps a state file to know which resources it manages. Makes it easy to track and update changes in AWS without accidentally del...
Read more