Service dependence

[Proskurin Kirill]

Hugo van der Kooij wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Proskurin Kirill wrote:
> |
> | define servicedependency{
> |         host_name                       host1
> |         service_description             Check RBL
> |         dependent_host_name             host1
> |         dependent_service_description   PING
> |         execution_failure_criteria      w,u,c
> |         notification_failure_criteria   w,u,c
> |         }
> |
> |
> | As im understand IF service Check RBL on host1 will be critical -
> | service PING will be critical too? But nofing happend.
> 
> No. It will mean that any depeding service will go to unreachable
> instead of critical.
> 
> So if you do not notify on unreachable services you will not be swarmed
> with critical alerts.
> 
> And the usage of whitespaces should be avoided to prevent mismatches.
> 

Thank you for respond.
1) It is will be seen on nagios what service is unreachable? Colors, 
messages? Then im do it on my test nagios - nothing is happend.

2) In my top post im ask this:

Im want to make this thing:

If check_alive service is critical(host is down) - do not check any
service on that host and *mark* it as critical.

And the same thing - if one service on remote host is critical - *mark*
as critical other service.

And, if it is possible, log to "Status Information" field what service1
critical because service2 is critical.

For example:
If check_mysql on host1 - critical
Mark as critical check_http on host2.
Status Information: "check_mysql on host1 - critical"

It is possible?

-- 
Best regards,
Proskurin Kirill

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
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