Business Process Overwrite state

[cmenapace]

Current Behavior

Right now if a service of a Business Process node is CRITICAL or WARNING the whole node goes to CRITICAL or WARNING

It would be helpful if we can influence the impact a single service has on its Business Process Node.
A single service, being a component may have a different level of importance for different business processes or as a stand-alone service. Therefore it would be useful to be able to map a service state to a new value from the business process perspective.

Possible Solution

A possible solution would be that on the service in a BP Node, we have the possibility to overwrite a certain state.

Example

WARNING -> OK
CRITICAL -> WARNING

If the service is WARNING, the service object in the BP Node remains OK, if the service goes to CRITICAL, it becomes WARNING in the BP
The real state of the service would be also visible in the BP service
I have Prepared a practice suggestion in Pull request #232

Use Cases

For example, while a critically full filesystem is a issue to solve fast, the business process it is part of, may not be impacted until the disk is completely full, so the service state should be addressed, but the impact on the business process is not (yet) critical. A mapping "Warning -> OK, Critical -> Warning" might be preferred.

An other example is a service-check witch monitors the connectivity to another system.
This service might be critical for a business process witch relays on real-time data, but the same service might be less important for a business process witch synchronize data in an hourly interval.
Therefore the importance from a business process perspective of the same service is different. While the first is impacted instantly by a failure on the service, the second not. So for the second, a mapping "Critical -> Warning" might be useful.
This service might be so important that, if the response time rises, the Business Process might be already impacted. (for example, users complaining about slow performance ect) So for this service in this business process a mapping "Warning -> Critical" might be desired.