Howdy,
I'm trying to design a multiple-inheritance structure for a new Nagios
3 setup. Consider the following:
define service{
name oracle
use fast,default
service_description Oracle Server
contact_groups +oracle_dba
check_command check_nrpe!check_oracle
register 0
}
define service{
name fast
retry_check_interval 2
normal_check_interval 5
register 0
}
define service{
name production
use default
contact_groups prod_responders
register 0
}
define service{
name filesystem
use slow,default
contact_groups +storage_admins
register 0
}
define service{
name slow
normal_check_interval 30
register 0
}
In this scenario "default" contains the default definitions, this is
sometimes written as "generic-service."
Now, for some examples: Production Oracle
define service{
use oracle,production
host_name lnx50
}
I expect by using production that prod_responders replaces the default
contact_group. Next, the additive (+) inheritance of oracle_dba
should create a union between the two contact_groups. Will this
declaration work as expected?
Next... an Production Oracle Filesystem
define service{
use filesystem,oracle,production
service_description Filesystem: /oradata
host_name lnx50
check_command check_nrpe!check_oradata
}
I only partially understand the precedence at work here. I understand
that it will operate with a "slow" check interval, but what about the
contact_groups? Since "filesystem" brings in the default early (with
it's own default contact groups), then does it ever add the
contact_group oracle_dba, or does it all get replaced by
production_responders?
Thoughts?
---
Caylan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
[email protected]
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
