Currently, the module does not handle well an icinga2 configuration including the config part at https://icinga.com/docs/icinga-2/latest/doc/03-monitoring-basics/#implicit-dependencies-for-services-on-host:
apply Dependency "disable-host-service-checks" to Service {
disable_checks = true
assign where true
}
The configuration above disables service checks for hosts identified as DOWN (HARD state).
Consequently, a service may still be considered OK if it has not been tested sufficiently to change its status to WARNING/CRITICAL/UNKNOWN HARD before the host changes to DOWN HARD.
To support that configuration, the Business Process module would need to check also the status of the host on which the service is configured: a BP node of type Service must first check the status of the related Host and if DOWN the Service node must return a CRITICAL.
Currently, the module does not handle well an icinga2 configuration including the config part at https://icinga.com/docs/icinga-2/latest/doc/03-monitoring-basics/#implicit-dependencies-for-services-on-host:
The configuration above disables service checks for hosts identified as DOWN (HARD state).
Consequently, a service may still be considered OK if it has not been tested sufficiently to change its status to WARNING/CRITICAL/UNKNOWN HARD before the host changes to DOWN HARD.
To support that configuration, the Business Process module would need to check also the status of the host on which the service is configured: a BP node of type Service must first check the status of the related Host and if DOWN the Service node must return a CRITICAL.