Every team has a different definition of when the part of the IT landscape they are watching over is in danger. So the View health state can be use to indicate when the whole, as defined in a view, is in danger. The View can be in three states:
Each view automatically has an associated View health state that is set by the !View health state configuration! that each view also has by default.
By default the view state is set
When the View health state changes it triggers a ViewHealthStateChangedEvent. This event can be used in !Event handlers! to, for example, trigger an e-mail or Slack message.
Configures how the View health state is determined from a summary of the components and relations in the view. By default the ‘default’ view health state configuration function will be used for a new view with
maxHealthStateDeviating set to 0 and
maxHealthStateCritical set to 0.
A view health state configuration function is a user defined script that takes user parameters and has access to a viewSummary variable that can be used to get summary information on the (states of) the components and relations in the view. There is always a ‘default’ View state configuration function available that will be used for new views.
To create, update or delete a view state configuration go to “Settings -> View Health State Configuration Functions”.