‫System monitoring can help users check on how much system resources are being used and which apps are
‫consuming what percentage of it.
‫It's very helpful.
‫It helps the user to properly manage the applications as well as make sure that the system is in good
‫health.
‫Of course, there are many built in tools available for system monitoring in Linux.
‫So we'll look at some of them.
‫So to see the status of disc death, which is an abbreviation for disc free, this is the command used
‫to display the amount of available disk space for file systems on which the invoking user has appropriate
‫read access.
‫The Dash H parameter print sizes in human readable format of.
‫Now, hopefully, you remember from the previous lectures, we already practiced the top command, so
‫top commanders used to show the Linux processes.
‫It provides a dynamic Real-Time view of the Running System.
‫Now, to see the status of RAM, the slash proc slash mem info file is another alternative way.
‫It's used to report the amount of free and unused memory on this system, as well as the shared memory
‫and buffers used by the kernel.
‫To check the status of the CPU, virtual memory statistics reporter, also known as VMS STAT.
‫This is a Linux command line tool that reports various bits of system information.
‫So slash proc slash CPU info is a short read only plain text file that contains information about the
‫CPU's or central processing unit on a particular computer.
‫Now, to check the status of the network, netstat can be used to list out all of the network socket
‫connections on a system.
‫There are some important parameters to that step.
‫Dashti is the parameter used to get TCP packets.
‫Dash N is used to avoid domain name resolution.
‫Dash L, this is a parameter used to list only the listening ports.
‫The dash parameters used to list the ID and name of the program, the Dash as parameter will get you
‫some statistics.
‫And, of course, a root parameter just plays the kernel routing table.
‫It must be so confusing to the UK users who say root and router.
‫Anyway, let's go to Carly.
‫And look how each tool works.
‫So first, let's run DFA dash each.
‫So as you can see, it displays the space available on all the currently mounted file systems.
‫If you happen to be using Mac OS, you can also run this in the terminal screen.
‫So let's go back to Carly, run the top command.
‫And these are the running processes with their kids usage, percentage of CPU memory, some other detailed
‫information.
‫And pressing you to quit.
‫Now, let's have a look at the content of these programs.
‫Info file.
‫So this whole display, the status of the RAM and the output of this command would be different depending
‫on the OS and architecture of the server.
‫All right, so let's continue with the status of CPU.
‫VM STAT provides a number of values and will typically be called using two numerical parameters.
‫Number two will provide the values and will be re measured and reported every two seconds.
‫Number five will provide the values that will be reported five times and then the program will stop.
‫All right, so now anticipating for you.
‫Now, the other way to get some information about the CPU is the Proc CPU info file.
‫As you can see, there's a lot of detailed information about CPUs such as model name, cache size,
‫speed, CPU cores and all that.
‫All right, so we'll have a look at the status of the network run, netstat, dash and LP.
‫That'll show the active connections with TCP packets and IDs.
‫So let's use netstat as parameter.
‫As you can see, the dash as argument will show overall stats.
‫And this is how you can pay attention to packets discarded messages.
‫And then finally, we can use the route parameter, or is it route parameter?
‫Well, I'm not if I'm a route user.
‫So the connections aren't working as expected because the connection goes through a different route.
‫It may be necessary to quickly check the routing table, so it includes information about how packets
‫are to be forwarded.
‫And it's stored in a kernel structure.