CCM - Service Dependency Management problem

[mcleodc]

Hi,

Whenever I add a new Server of switch to nagios I create a Service Dependency using the CCM for that host/services. Basically making all services dependant on Ping and NSClient for servers.

Normally when i click add in CCM - Advanced - Service Dependencies and select the new host in both the "Host" section and "dependant hosts" section I get a list of services associated with that host only. But today when I have done this I am seeing many more services from other hosts. Also when I have done this in the past the services selection section remains blank until after a host has been selected but now a list of services are available for selection before a host is selected.

I am running 2011R2.1. I am not sure if this is since the upgrade as I have not added a Dependency in a few weeks.

Thanks
Chris Macleod

[scottwilkerson]

This is since the upgrade. It was a change that needed to be made to support dependencies of services that are not directly tied to a host.

For example you could have a service that doesn't have any hosts but has host groups assigned, and all hosts in the hostgroup automatically get that service...

In the old form, you couldn't select the service until you selected a host, but you may not be selecting a host, wildcard hosts.

[mcleodc]

Hi Scott,

So I should see a list of every service i have configured or just services that are no asociated with a host or hostgroup?

Also my dependency definitions are dependant on the ping service - this service doesn't show as being selected now. What could have caused this? The ping service for most of my hosts is named "Ping" this has been removed from the selected service box. I notice i have the service "PING" available for selection (uppercase).

Thanks
Chris

[scottwilkerson]

I'm going to have to dig into this a little and check with a few of the developers on this.

[mcleodc]

Thanks Scott.

Looking in the actual servicedependencies.cfg file I can see Ping is there. Would seem the problem might be with the fact I have a couple of services named PING all in uppercase. Would simply renaming these to "Ping" help.

Here is a sample from my servicedependencies.cfg file

define servicedependency {
dependent_host_name KORFP1
dependent_service_description CPU Usage,Drive C: Disk Usage,Drive D: Disk Usage,IIS Web Server,Logon Errors,Memory Usage,Page File Usage,Printer Spooler,Server Work Queues,Uptime
host_name KORFP1
service_description NSClient,Ping
inherits_parent 1
execution_failure_criteria w,u,c
notification_failure_criteria w,u,c
dependency_period 24x7

in the CCM I only see nsclient as selected. PING is available for me to select if I want.

[mguthrie]

The issue we were having with service dependencies and escalations is that people couldn't select their services they were looking for if they had service->hostgroup relationships. The list would never populate with services if they had this kind of a setup. So what we changed is that now there is a flat list of all unique service descriptions populated in that field, so the definitions now work pretty much the same as they do with Nagios Core. You simply pick your host or hostgroup, and then the service description you're looking to match for the dependency.

Hope that helps.