Werk #6706: BI availability no longer creates N/A periods if an element within the BI was not known at the time
| Component | User interface | ||||||||||||||
| Title | BI availability no longer creates N/A periods if an element within the BI was not known at the time | ||||||||||||||
| Date | Feb 19, 2019 | ||||||||||||||
| Level | Trivial Change | ||||||||||||||
| Class | Bug Fix | ||||||||||||||
| Compatibility | Compatible - no manual interaction needed | ||||||||||||||
| Checkmk versions & editions |
|
WK:4202 introduced some special handling for BI aggregations:
When computing the availability of a BI aggregation for a time range during which new hosts or services were added to the monitoring the state of these objects would be displayed as PEND before point of time they were added. But this is not correct. These objects where not pending but simply not yet existing and thus not contained in the aggregation tree at all at that time.
This introduced an side effect, so that some availability reports of an aggregation still shows N/A even when the user has explicitly switched off Include unmonitored time.