<span style="color: rgb(0, 0, 153);">Depending on what type of Linux system you are monitoring, the type/need of/for tools varies.</span><br style="color: rgb(0, 0, 153);"><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">If you are going to monitor a destop system, then there are a multitude of karamba/superkaramba/gdesklets available which gives you the network, hard-disk, cpu information every few seconds, some easily changed as they are scripts, others need some tinkering using python.</span><br style="color: rgb(0, 0, 153);">
<br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">If you are monitoring a server, then you will need to script the things you would like to monitor using tools either already present or installing them additionally. The easy way is to either program you script into a desktop applet or send it to an html file which is updated at a said interval.</span><br style="color: rgb(0, 0, 153);">
<br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">Tools you would need are:</span><br style="color: rgb(0, 0, 153);"><ol><li><span style="color: rgb(0, 0, 153);">sensors ( to monitor the voltage and temperature of the cpu, fan and motherboard)</span></li>
<li><span style="color: rgb(0, 0, 153);">hddtemp (to monitor the temperature of your hard-disks)</span></li><li><span style="color: rgb(0, 0, 153);">hwinfo (to keep your hardware configuration available when server hardware fails, good for disk serial number and firmware version)</span></li>
<li><span style="color: rgb(0, 0, 153);">dmidecode (to keep track of your hardware serial number, firmware version and BIOS info - useful when calling vendors)</span></li><li><span style="color: rgb(0, 0, 153);">iostat, mpstat, sar, top and vmstat to get the statistics or the current state of the live system.</span></li>
<li><span style="color: rgb(0, 0, 153);">smartmontools (useful to monitor disk degradation / failures)</span></li></ol><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">Hope this helps. </span><br style="color: rgb(0, 0, 153);">
<br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">-GGR</span><br style="color: rgb(0, 0, 153);" clear="all"><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">--</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">Rajiv G Gunja</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">Blog: <a href="http://ossrocks.blogspot.com">http://ossrocks.blogspot.com</a></span><br>
<br><br><div class="gmail_quote">2009/1/26 Jason Dixon <span dir="ltr"><<a href="mailto:jason@dixongroup.net">jason@dixongroup.net</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Mon, Jan 26, 2009 at 04:21:19PM -0500, Jason C. Miller wrote:<br>
><br>
> On Mon, 26 Jan 2009, Jason Dixon wrote:<br>
><br>
>> On Mon, Jan 26, 2009 at 04:14:41PM -0500, Jason C. Miller wrote:<br>
>>> Hey all. :)<br>
>>><br>
>>> I'm looking for a good way to monitor resource usage for a linux machine.<br>
>>> Redirecting 'top' to a file only goes so far and I'm NOT looking to do<br>
>>> something as drastic as SNMP. Here's what I'm looking for<br>
>>> in a solution:<br>
>>><br>
>>> 1. No extra software purchase/download necessary<br>
>>> 2. If software download is mandatory, that it be extremely minimalistic<br>
>>> 3. Uses the default linux toolbox of utilities<br>
>>> 4. Something thorough (seperate CPUs, memory, I/O)<br>
>>><br>
>>> It could be that something simple already exists and that I've missed it.<br>
>>> If you know of a cool utility, script, or method that I can use to<br>
>>> accomplish this, please chime in.<br>
>><br>
>> There's nothing drastic about SNMP. It's very simple once you have the<br>
>> basic command string and was designed for what you want.<br>
>><br>
> True. But I would like some fine-grained statistics (per second, if<br>
> needed) without muddying the network. This just skews the I/O results<br>
> anyway.<br>
<br>
</div>You can pull SNMP queries as often you like. SNMP != rrdtool. It only<br>
skews your results if you're querying from another system. The same is<br>
true for *any* administrative traffic you'd use to monitor the system<br>
remotely.<br>
<div><div></div><div class="Wj3C7c"><br>
--<br>
Jason Dixon<br>
DixonGroup Consulting<br>
<a href="http://www.dixongroup.net/" target="_blank">http://www.dixongroup.net/</a><br>
<br>
_______________________________________________<br>
CALUG mailing list<br>
<a href="mailto:CALUG@unknownlamer.org">CALUG@unknownlamer.org</a><br>
<a href="http://lists.unknownlamer.org/listinfo/calug" target="_blank">http://lists.unknownlamer.org/listinfo/calug</a><br>
</div></div></blockquote></div><br>