-----Ursprüngliche Nachricht-----
Von: Danilo Godec [mailto:danilo.go...@agenda.si]
Gesendet: Montag, 30. August 2010 11:03
An: Nagios Users List
Betreff: [Nagios-users] Are service contacts 'inherited' from respectivehost?
Hi,
I'm monitoring a bunch of hosts and each of these hosts has at least two
services used to monitor and graph ping RTA and packet-loss. Hosts
configurations are organized in several .cfg files (by building), there is also
a hostgroup definition grouping all hosts in a building.
However, hosts in a building can have different contacts...
I defined services using hostgroups - like this:
define service {
use template
hostgroup_name MYHOSTGROUP
}
I was hoping a service that doesn't have a contact definition would 'inherit'
the contact from the host - but it seems that's not the case.
Is there a way to make that happen? Or will I need to define services
one-by-one while and add contact definition to each?
Danilo
Hi,
What Nagios version do you use?
Since Nagios 3.0 contact_groups, notification_interval, notification_period are
inherited from the related host definition if you don't explicitly specify them
in the service object or an inherited template.
http://nagios.sourceforge.net/docs/3_0/objectinheritance.html
Gerald
OOe. Gesundheits- und Spitals-AG
Techcenter, Hafenstrasse 47-51, 4020 Linz DVR 2107870, ATU 51928204,
Firmenbuchgericht: Landesgericht Linz, FN 210146 p
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Nagios-users mailing list
Nagios-users@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
