Service Group Management Bug?

[kyle.parker]

We use service groups in our network as I am sure most people do. I came across an odd issue where if you add the service to the service group during the config wizard it can only be removed at a later date by going to that service in the CCM and manually removing it under the service management page. If you go into the manage service group and click on manage services in the list they will be greyed out and have an => next to them, which tells you "Object relationship elsewhere".

This caused an issue for me when I had to removed 400 services from a service group. I was unable to do it from the service group management page because they were all added to the service group during the config wizard and had to manually do it one by one which took me a few hours.

I wasn't sure if this was the way it is supposed to work or if this is some sort of glitch that can be patched in a future release, but I wanted to bring this to a dev's attention in case it is a glitch.

[jdalrymple]

No glitch,

hostgroups and servicegroups have kind of anomoly that dates back to the original core days. They can be defined in 2 ways...

Servicegroup definitions can have services added to them
Service definitions can be added to servicegroups (what you saw)

Host definitions can be added to hostgroups
Hostgroup definitions can have hosts added to them

The end result is the same - organization might me more convenient using one method or the other depending on your use case. Unfortunately adding hosts and services by wizard creates pretty "static" configurations that are a bit less modular and more time-consuming to change.

Make sense?

[Box293]

This would be a good addition to the Bulk Modifications Tool.