Werk #721: Use hard states in BI aggregates
| Component | BI | ||||||||||||||||||
| Title | Use hard states in BI aggregates | ||||||||||||||||||
| Date | Mar 10, 2014 | ||||||||||||||||||
| Level | Prominent Change | ||||||||||||||||||
| Class | New Feature | ||||||||||||||||||
| Compatibility | Compatible - no manual interaction needed | ||||||||||||||||||
| Checkmk versions & editions |
|
Check_MK BI is now able to base the computation of the state of a BI aggregate on hard states of hosts and services. This is a new option at the top level of a BI aggregate. In WATO this is a new check box in each aggregation called Base state computation on hard states.
When you edit your BI aggregates with a text editor then simply prefix your aggregation entries with the keyword HARD_STATES. Here is an example:
etc/check_mk/multisite.d/mybi.mk
host_aggregations += [
( HARD_STATES, 'Hosts', FOREACH_HOST, ['tcp'], ALL_HOSTS, 'host', ['$1$']),
]
Note 1: Hard states only make sense if you have changed the Maximum Number of Check Attempts of a host or service from the default value of 1 to a higher value. If you have set the number of attempts to three the hard state of service remaines OK until the service has been checked three times in a row with a non-OK state.
Note 2: Please make sure that all of your monitoring sites are updated to the same Check_MK version as your Multisite server. This new BI features needs an up-to-date Livestatus implementation.