Nagios Support Forum

I noticed strange behavior in the service escalation management screen, the "services selection pop-up screen" to be exact.

Normally within an service escalation you will select a host and in the "services selection pop-up screen" you will see in the left list all the services belonging to that host. Bringing services to the right side will make them active for that escalation service.

Today I want to make a change within an escalation service and remove a service for a host. However on the right side I see only 4 services active instead of about the 30 services I expected and on the left side I don't see the services belonging to that host, but all the services that exits regardless of the hosts they belong to. It looks like the host/services relationship has broken in that screen?

I also checked the file /usr/local/nagios/etc/serviceescalations.cfg which show the correct configuration as expected.

We currently have R2.1 installed, I'm not sure at which release it was still working correctly for us.

You may have to upgrade to 2011R2.2, in which we fixed an issue where the unique service descriptions that populated the service escalations page were case insensitive. See bellow:

http://assets.nagios.com/downloads/nagi ... S-2011.TXT

Thanks for the reply,

the R2.2 update is on my to-do list for this week anyway, I'll see if I can get to it tomorrow. I'll keep you posted what the result of the update is.

Greetings..Hans

Hello,

just finished to update from R2.1 to R2.2. Unfortunately the above problem is not solved by the fixes in R2.2.

Greetings..Hans

Hi Hans,

Sorry for the confusion on our end, I thought the issue was something else we came across for the 2.1 version. We changed the display logic for service escalations a few versions ago. The reason for the change was that users who had assigned service->hostgroup relationships were not able to create service escalations at all. So the select lists now populate with a list of all unique service descriptions to allow for those assignments to take place. Basically the service escalations and service dependency pages now function more like the Core configs underneath. This does remove a bit of the controlled input from the user perspective, but we felt it was more important that we allow for the flexibility because some users couldn't use the CCM to create service escalations at all.

Hi Mike,

"unique service description" gave me a good shock. So basically if I have 70 unix host and all of them have a service called "/var", only one of those will be shown in the list on the left side?
The "service->hostgroup relationships" comment rings a bell, I believe I made a call about that last year, but I thought it was going to be resolved during the core rewrite of 2012.

I'm going to have a good think over tonight and do some testing tomorrow. If the "service->hostgroup relationships" does work now I should perhaps go back to my initial plan of creating generic services and assign them to host/hostgroups. Anyway the way the screen works now, it's non-functional to us.

Greetings..Hans

If you have 70 services with the service description of "/var", that shouldn't make any difference. The configs get compiled down so that in the end the service escalation is assigned as a single host->service combination. The core configs don't use ID's, they only use the host_name, and service_description as identifiers.

So even if I have an escalation defined with multiple hosts and multiple services:
It gets compiled down to the following definition in the objects.cache file that the Core engine uses.

The only things that the new version does is change how the UI displays the list of selectable services.

Hi Mike,

I ran some test with the service escalation and it works fine. It's only the existing escalations that are shown incorrectly in the GUI (but indeed in the core they are as they are supposed to be).
I was planning some big changes to our escalations anyway, so I'm going to delete the existing ones and recreate them with our new changes. That seems to cure our "missing" services.

Thanks for your help

Greetings...Hans

Ok, glad to hear the configs are still being creating correctly Let us know if you have any more questions.