Nagios Support Forum

Recently we have upgraded nagios XI from 2014R1.2 to 2014R2.0 Till upgrade I’ve used the old CCM to configure the host and services. When I configure the service escalation, for the “Manage services” the old CCM was just listed the “service description” (eg: PING) and I needed to select the relevant service description once for multiple “Manage Hosts”.

But now in the new CCM I’m seeing the host-service description mapping (eg: host1-PING) listed under “Manage services”. In this case if I need to create an escalation for PING check with multiple manage hosts, do I need to select all relevant in the “Manage services” too?

Thanks

westernuniv wrote:do I need to select all relevant in the “Manage services” too?

Yes. Though, I don't think a service set up with object tricks worked before either.

I already have many service escalations created in old CCM
Eg:
Managed hosts: host1, host2, host3
Manage Services: HTTP

After the upgrade, in the new CCM, I only see the first host associated with the service was selected as below
Managed hosts: host1, host2, host3
Manage Services: host1-HTTP

I’ve done some testing and the escalation worked for Host2. When I looked at the nagios config file: serviceescalations.cfg, there is no change at all.

define serviceescalation {
host_name host1,host2,host3
service_description HTTP
contacts john, adam
first_notification 2
last_notification 0
notification_interval 2
escalation_period 24x7
escalation_options c,r,
}

Is there any bug in new CCM representing the managed services then?

Thanks

Possibly. If you can use the old legacy ccm, please do so and we will look at this issue for an upcoming release.

In the latest XI 2014R2.0 release, there is no option provided to use the legacy CCM. We do have service escalations which uses the "Host group" with hundreds of host and it's really confusing us what to select under "Manage services". Could you open a bug report and get this fixed in the upcoming release?

Thanks

I filed an internal bug report (TASK ID 4673). I expect this to be fixed in the next release of Nagios XI. Thanks!

That's great. Thank you

We'll go ahead and close this thread for now. Thanks.