xception: Sar for more than 7 days

<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d11356004\x26blogName\x3dxception\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttps://openrent.blogspot.com/search\x26blogLocale\x3den_US\x26v\x3d2\x26homepageUrl\x3dhttp://openrent.blogspot.com/\x26vt\x3d-4655156434419967503', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe", messageHandlersFilter: gapi.iframes.CROSS_ORIGIN_IFRAMES_FILTER, messageHandlers: { 'blogger-ping': function() {} } }); } }); </script>

Sar for more than 7 days

By default, the sar (system activity report) utility only keeps 7 days worth of records. Seven days is usually not long enough to capture enough data for meaningful trend analysis. You can therefore change the the duration of time that sar tracks system activity by editing the /etc/sysconfig/sysstat file from this:

# How long to keep log files (days), maximum is a month
HISTORY=7

# How long to keep log files (days), maximum is a month
HISTORY=30

This will give you 30 days of log files to chew on. You could also setup a cron job that runs a script to copy the previous days data file to another directory, renaming the files to (YYYYMMDD) instead of just the day (DD) each time. This will give you even more than 30 days worth of data to review.