Put hosts in hostgroups and apply the hostgroups to services. Hosts can then be disabled w/o CCM getting upset even if there are no active hosts applied to a service.
I jst verified by creating a host, hostgroup with that host, and a service with the hostgroup, then deactivated the host and applied w/o error.
Since "active/inactive" is a database thing, the CCM could "cascade" the inactive host to deactivate all services that are assigned to it so that when Core is restarted, those things are ignored.
Edited for grammar.
Last edited by eloyd on Fri Jul 14, 2017 8:43 am, edited 1 time in total.
While this is a workaround, it does not change my mind that the underlying functionality that I described should still exist.
gormank wrote:Put hosts in hostgroups and apply the hostgroups to services. Hosts can then be disabled w/o CCM getting upset even if there are no active hosts applied to a service.
I jst verified by creating a host, hostgroup with that host, and a service with the hostgroup, then deactivated the host and applied w/o error.