escalations for large shop
Jeff Williams
jeffwilliams05 at gmail.com
Thu Jan 12 16:14:38 CET 2006
On 1/11/06, David Schlecht <dschlecht at doit.nv.gov> wrote:
> Hi list
>
>
>
> Does notification escalation scale well to large shops?
>
> From the docs it appears that each host/service pair must
>
> have its own record in the serviceEscalations.cfg file. I see
>
> no support for host groups.
How big of a shop are you talking about? 1000 hosts? 10000 hosts? more?
> If I have to enter and maintain many hundreds of host/service
>
> pairs in the config file, I need a raise!
>
>
>
> Has anyone with a large shop been successful at this?
>
>
>
> According to the docs, HOST escalation definitions have a
>
> hostgroup_name field which allows multiple host groups, but
>
> this field is optional and the host_name field is required.
>
> Is it possible that if hostgroup_name is defined, then the
>
> host_name field can be skipped? They seem mutually exclusive.
>
>
>
> Allowing host groups for services would be real nice, too.
>
I have a large number of hosts that have common services. A nice thing
you can do is just specify the service/escalation once and just have
multiple hostnames delimited by comma. I find it nice to have
individual files for each host, specifically for their host-specific
information, rather than lumping all of that into one host.cfg file,
but that's a matter of personal preference.
I'm in the middle of a Nagios setup and we will probably have anywhere
from 1000-1500 unique hosts, some with many services and others with
only ping and/or snmp. I already have around 100 of our servers in
there, each of which has around 15 of its own services. I've been
looking at Fruity (a web-based configuration tool), but I have been
unable to get it to import my current escalations. You may want to use
something like this unless you are going to write a script for
yourself to speed the host/service/escalation creation process. Fruity
may work very well for you since it sounds like you are still
preparing to add all your hosts. However, it is not recommended for
production use, but that means you should just make regular backups of
your config files and be careful about exporting.
Hope some of this helps.
Regards,
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
More information about the Users
mailing list