Re: monitoring and alerting software ????
From: Mike Woods (Mike_at_the-rubber-chicken-network.co.uk)
Date: 05/14/05
- Previous message: Chuck Swiger: "Re: monitoring and alerting software ????"
- In reply to: Warren Block: "Re: monitoring and alerting software ????"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 14 May 2005 12:44:41 +0100 To: Warren Block <wblock@wonkity.com>
Warren Block wrote:
> On Thu, 12 May 2005, Duane Winner wrote:
>
>> Does anybody have recommendations for a good solution to alert me
>> while I am not at work if something goes wrong with my
>> infrastucture/network/servers?
>> In other words, if I am at home, I need to be alerted if one of my
>> FreeBSD servers go down, but also if the router, firewall or switches
>> go haywire.
>
>
> Here's something I wrote recently on setting up Nagios on FreeBSD:
>
> http://www.wonkity.com/~wblock/nagios.pdf
Nagios is a good choice indeed, i've recently implemented a monitoring
system for our rack at redbus using Nagios and i'm rather impressed with
how well it all works!
I've picked up a couple of "tricks" while doing this, the first one is
simply to make very good use of service templates, most of the services
we monitor in our rack are websites (using check_http) so that becomes a
somewhat repeating entry in the config, to minimize this i have a
template defined for website checks containing all of the static values
which looks an awful lot like this
define service{
use generic-service
name website-service
is_volatile 0
check_period 24x7
max_check_attempts 5
normal_check_interval 1
retry_check_interval 1
contact_groups admins
notification_interval 240
notification_period 24x7
notification_options w,u,c,r
register 0
}
since the check command will be different for each site since the site
address to query is included that gets specified in the site description
resulting in an entry that looks a lot like this
define service{
which greatly reduces the size of my config files and makes them a whole
The other trick i've picked up is split all my host definitions into
Last two things, firstly, nagios -v is your friend, it will give you
Hope that's helpful to someone :)
---------------------
use website-service
host_name <ServerName>
service_description <ServiceName> (I use sitename)
check_command check_site!http://
}
lot easier to maintain!
individual files for each host then add an entry for them in the main
Nagios config (much as i do with vhosts in apache), again this makes it
far easier to maintain and has the bonus that removing a host is simply
a matter of commenting out/deleting a line in the master config file.
concise and quite useful information on any errors in your config files
and saves you loosing the system because of a typo, secondly, for
remote checks nrpe is a godsend, it can be used to allow Nagios to check
pretty much any local information on a remote machine and is quite easy
to configure, for example I have it monitoring the capacity of the /usr
mount our Solars machine (along with a few other bits).
Mike Woods
Systems Administrator
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Relevant Pages
... Suse setups nagios as such ... /etc/nagios - config files ... AllowOverride AuthConfig ...
(SuSE)
... Browsing the check_ntp.pl Nagios "plugin", which I guess is what is ... associated to a host, ... second offset from the monitored host, ... the host where *the monitoring function* is running... ...
(comp.protocols.time.ntp)
... I run nagios from one of our hosts... ... the other day it began reporting ... ping from the nagios host to the site ended with "network ... while a traceroute from the same host succeeded. ...
(comp.os.linux.networking)
... Nagios) ... dass einfach der Host überlastet ist? ... wenn nur eine oder zwei VMs laufen ... Yusuf Dikmenoglu ...
(microsoft.public.de.german.windows.server.networking)
... Nope not just you, 1k hosts and the system was almost unusable on a dual amd mp2800, in the end I wrote my own monitoring system running from a db backend and achieved the same results as nagios with 1/50th the actual load whilst also keeping historical data in a db. ... Nagios is great if you need the multitude of host checks for a core network, but if you're just after something to check host connectivity it may not be the right tool for the job. ...
(freebsd-isp)
