Hi all:
Not sure if 2.0 was supposed to be supported on the main nagios list
or not, and since this deals with bugs and development ideas, I figured
here would be better.
One bug is preventing clear notifications when using
servicedependencies.
Also there are a couple of doc bugs.
Also as a feature, I would loke a way to set up dependencies between
two services running on the same machine using specifying multiple
host/hostgroups.
First for the bugs major to minor:
I am not geting a proper clear notification when using
servicedependencies.
I have four services each depending on the other.
Using my check_test plugin I set up the following:
define service{
use generic-service
host_name web_server1
service_description web_service2
is_volatile 0
check_period 24x7
max_check_attempts 3
normal_check_interval 1
retry_check_interval 1
contact_groups admins
notification_interval 15
notification_period 24x7
notification_options w,u,c,r
check_command check_web1
}
which is duplicated for every service (except for a different check
command).
define servicedependency {
name dependency_template
execution_failure_criteria n
notification_failure_criteria w,u,c
register 0
}
define servicedependency {
use dependency_template
dependent_host_name web_server1
dependent_service_description web_service2
host_name web_server1
service_description web_service1
inherits_parent 1
}
define servicedependency {
use dependency_template
dependent_host_name web_server1
dependent_service_description web_service2.1
host_name web_server1
service_description web_service2
inherits_parent 1
}
define servicedependency {
use dependency_template
dependent_host_name web_server1
dependent_service_description web_service2.1.1
host_name web_server1
service_description web_service2.1
inherits_parent 1
}
define servicedependency {
use dependency_template
dependent_host_name web_server1
dependent_service_description web_service3
host_name web_server1
service_description web_service2
inherits_parent 1
}
If I set three services to critical:
service2.1.1 which depends on service2.1 which depends on
service2
I correctly get critical notification only for service 2.
Now if I put service1 (which is depended on by service2) in critical
mode and let that notification go through, and then bring service2 up
(ok), I get the service down notification for service1, but I never
get a service up notification for service2.
Service2 is displayed as OK in the web interface.
When I set service1 to ok, I get the notification of ok status for
service1 as expected, but I don't get a delayed or other notification
for service2 in the OK state.
Also I get the service critical alert for service2.1 as expected.
I think that the notification for service2 should be sent since a
critical alert went out for it. This is needed when a different group
of people respond to the service2 event as compared to the service1
event. If the down notification for service2 never went out I wouldn't
be concerned. I could also agree (but somewhat less strongly) with
sending the OK status for service2 out after service1 goes to an OK
status.
BUG2
The use of hostgroups in the service dependency definition:
/nagios/docs/xodtemplate.html isn't documented.
BUG3
If you set up a service dependency and use the "inherit_parent" parent
directive and set it to "yes" rather then 1, nagios doesn't give you
an error, it treats it as a 0. It should probably complain.
FEATURE REQUEST
A way to set up dependencies between two services running on the same
machine using specifying multiple host/hostgroups. When you have a farm
of machines, it is useful to be able to specify the dependen
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]