Changing some properties in the Alignak objects stored in the backend would not make Alignak monitoring framework reload the configuration and restart the checks scheduling: host position, host alias, ...
Those properties are not necessarily involved in the monitoring process ... and the configuration reload is not necessary. Changing the host position on the map would not make the monitoring restart indeed !
Those properties sould be marked as 'making/not making Alignak monitoring framework restart'
Changing some properties in the Alignak objects stored in the backend would not make Alignak monitoring framework reload the configuration and restart the checks scheduling: host position, host alias, ...
Those properties are not necessarily involved in the monitoring process ... and the configuration reload is not necessary. Changing the host position on the map would not make the monitoring restart indeed !
Those properties sould be marked as 'making/not making Alignak monitoring framework restart'