…….mainly because it has saved me from being totally unaware of “stuff going wrong”!  Just a few words for the uninitiated though:-

• Use a GUI config tool, not because the config files are hard to understand but more because its easier to do templates, creates parent/child relationships and see the logic of your setup.  I use Fruity, which is great apart from it won’t help you get your configs right when you have messed something up.
• There are many ways to skin the Windows cat with Nagios and my current favourite client is nc-net but you will probably need SNMP too (especially if you want to monitor hardware).
• Always cross monitor and always from another physically separate location.  There is nothing worse than not knowing that your monitoring server is down (apart from your whole location being down AND you don’t know about it until the MD/Chairman/Major Shareholder is on the phone to you!).
• If you have a wiki with info on your servers then link your Nagios hosts into the wiki via the “extended info” sections of the configs.

Tags: Nagios

This entry was posted on Thursday, May 29th, 2008 at 6:40 pm and is filed under Nagios. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.