Glen Pitt-Pladdy :: Blogvmstat on Cacti via SNMP | |||
After a long silence I've finally got round to releasing these templates. The theme is rather simple: take a standard tuning tool and with a tiny bit of scripting deliver it's output via SNMP for Cacti to graph. This gives you always-on data about the performance of a system and allows unexpected changes to be easily spotted on Cacti graphs. vmstat to SNMPLike I described previously in my SNMP Basics article, I run a cron job to pick up data and dump it in files where snmpd can pick it up as a low privilege user. I'm doing the same here, except that I'm using it to run vmstat in the background to collect data over the polling period. Download: all the iostat Cacti scripts, files and templates are now on GitHub Take the data collection script vmstat-cron, make this executable and stick it somewhere convenient. I will assume /etc/snmp for this article with the output files in /var/local/snmp. Then add to the SNMP cron job (described previously) some lines to run this in the background: # background the vmstat run That will launch vmstat in a wrapper which will run for 5 minutes (300 seconds) outputting to a temporary file and rename the temporary file to the name given as the first argument. You can easily alter the script if you poll more/less frequently. Check that the output file is being created and has data in it - it will take 5 minutes from the next cron run before the file is created. Next, to get the data into snmpd add the following to the /etc/snmp/snmpd.conf file: extend vmstat /bin/cat /var/local/snmp/vmstat That simply picks up the contents of the file when SNMP is queried. Restart snmpd and you should be able to test that with snmpwalk as described in previous articles. SNMP to CactiImport the Cacti template cacti_host_template_vmstat.xml and add it to the host you have configured above. Add the graphs and all going well after a couple polls data should start appearing on the graphs. What it looks like |
|||
Disclaimer: This is a load of random thoughts, ideas and other nonsense and is not intended to be taken seriously. I have no idea what I am doing with most of this so if you are stupid and naive enough to believe any of it, it is your own fault and you can live with the consequences. More importantly this blog may contain substances such as humor which have not yet been approved for human (or machine) consumption and could seriously damage your health if taken seriously. If you still feel the need to litigate (or whatever other legal nonsense people have dreamed up now), then please address all complaints and other stupidity to yourself as you clearly "don't get it". This site uses cookies stored for for generating usage statistics and makes use of Google Analytics with it's own policies.
Copyright Glen Pitt-Pladdy 2008-2019
|
Comments:
thanks, Glen
My cs and in graph seem identical? and yours seems missing, so can"t compare.
Thanks for pointing out the missing graph - fixed.
In my case "cs" and "in" are similar, which is not unexpected since they will relate to some common things like the level of activity on the system. One thing to check is the items in the stats file - I believe items 11 and 12 should be these two, and also just run vmstat yourself (300 second samples) to check the numbers stack up.