Everything Penguin

Focusing on Linux-based Operating Systems
htDig Search:

Operating Systems
  • /pub/OS/Linux

  • Storage
  • File Systems
  • HPC
  • /pub/Storage

  • Networking
  • /pub/Networking

  • Network Services
  • /pub/NetworkServices

  • Security
  • /pub/Security
  • Keytool/OpenSSL

  • Clustering
  • HA
  • DRM

  • Development
  • Design
  • C/C++
  • Java
  • Perl
  • Python
  • Shell
  • Web / J2EE

  • Not Linux ?
  • BSD
  • HP-UX
  • Mac
  • Solaris
  • VM
  • Windows
  • /pub/OS

  • Other
  • /pub
  • /pub/3rdParty
  •  Parent Directory

    Sar - Part 2
    Brett Lee
    ===============================================
    
    
    I'm not sure why this is even necessary.  There is an excellent man page.
    
    Look, there's even usage:
    
         $ sar help
         Usage: sar [ options... ] [ <interval> [ <count> ] ]
         Options are:
         [ -A ] [ -b ] [ -B ] [ -c ] [ -d ] [ -i <interval> ] [ -p ] [ -q ]
         [ -r ] [ -R ] [ -t ] [ -u ] [ -v ] [ -V ] [ -w ] [ -W ] [ -y ]
         [ -I { <irq> | SUM | ALL | XALL } ] [ -P { <cpu> | ALL } ]
         [ -n { DEV | EDEV | NFS | NFSD | SOCK | ALL } ]
         [ -x { <pid> | SELF | ALL } ] [ -X { <pid> | SELF | ALL } ]
         [ -o [ <filename> ] | -f [ <filename> ] ]
         [ -s [ <hh:mm:ss> ] ] [ -e [ <hh:mm:ss> ] ]
    
    
    
    
    Ok, here are the arguments in order (from above):
    -----------------------------------------------------
    
    ** Note: For an explanation of the fields reported by sar, see the man page.
      ^^^^^^
    
    
      -A     Equivalent to specifying -bBcdqrRuvwWy -I SUM -I XALL -n ALL -P ALL
    
      -b     Report I/O and transfer rate statistics.
    
      -B     Report paging statistics.
    
      -c     Report process creation activity.
    
      -d     Report activity for each block device (kernels 2.4 and newer only).
    
      -i <interval>
             Select data records every <interval> seconds.
    
      -p     Pretty-print device names.
    
      -q     Report queue length and load averages.
    
      -r     Report memory and swap space utilization statistics.
    
      -R     Report memory statistics.
    
      -t     Report timestamps in the original locale.
    
      -u     Report CPU utilization.
    
      -v     Report status of inode, file and other kernel tables.
    
      -V     Print version number then exit.
    
      -W     Report swapping statistics.
    
      -y     Report TTY device activity.
    
      -I { irq | SUM | ALL | XALL }
             Report statistics for a given interrupt.
    
      -P { cpu | ALL }
             Report per-processor ( <cpu> ) or all ( ALL ) statistics.
    
      -n { DEV | EDEV | NFS | NFSD | SOCK | ALL }
             Report network statistics.
    
      -X { pid | SELF | ALL }
             Report statistics for a PID, SELF (the sar process) or ALL processes.
    
      -X { pid | SELF | ALL }
             Report statistics for the child processes of a PID, SELF (the sar 
             process) or ALL processes.
    
      -o [ <filename> ]
             Save the readings in the file in binary form.
    
      -f [ <filename> ] ]
             Extract records from filename (created by the -o filename flag).
    
      -s [ hh:mm:ss ]
             Set starting time of the report (default is 08:00).
    
      -e [ hh:mm:ss ]
             Set ending time of the report (default is 18:00).
    
    
    
    
    ** A bit overwhelming?
    ---------------------------
    
    Points to remember:
    
      1. sar collects this stuff continuously.  It is there when needed.
    
      2. sar deletes the data from /var/log/sa after about a week.  If
         historical data is desired, back it up.
    
      3. Displaying these data visually is not as overwhelming and provides
         a great way to get started with analyzing the data.
    
      4. sadf provides the ability to export saXX files into XML and CSV
         so that visualization and processing are simplified.
    
      5. Some cisualization tools are listed in "Reference_SAR_1.txt"
    
    
    
    
    
    

    Other Sites

    RFC's
  • FAQ's
  • IETF
  • RFC Sourcebook

  • Linux
  • Linux - Intro
  • Linux Kernel
  • Linux Kernel (LKML)
  • Bash - Intro
  • Bash - Advanced
  • Command Line
  • System Administration
  • Network Administration
  • Man Pages (& more)
  • More Guides
  • Red Hat Manuals
  • HOWTO's

  • Reference/Tutorials
  • C++ @ cppreference
  • C++ @ cplusplus
  • CSS @ echoecho
  • DNS @ Zytrax
  • HTML @ W3 Schools
  • Java @ Sun
  • LDAP @ Zytrax
  • Linux @ YoLinux
  • MySQL
  • NetFilter
  • Network Protocols
  • OpenLDAP
  • Quagga
  • Samba
  • Unix Programming



  • This site contains many of my notes from research into different aspects of the Linux kernel as well as some of the software provided by GNU and others. Thouugh these notes are not fully comprehensive or even completetly accurate, they are part of my on-going attempt to better understand this complex field. And, they are your to use.

    Should you wish to report any errors or suggestions, please let me know.

    Should you wish to make a donation for anything you may have learned here, please direct that donation to the ASPCA, with my sincere thanks.

    Brett Lee
    Everything Penguin

    The code for this site, which is just a few CGI scripts, may be found on GitHub (https://github.com/userbrett/cgindex).

    For both data encryption and password protection, try Personal Data Security (https://www.trustpds.com).


    "We left all that stuff out. If there's an error, we have this routine called 'panic', and when its called, the machine crashes, and you holler down the hall, 'Hey, reboot it.'"

        - Dennis Ritchie on Unix (vs Multics)


    Google
    [ Powered by Red Hat Linux ] [ Powered by Apache Server] [ Powered by MySQL ]

    [ Statistics by AWStats ]