Werk #22700: BI: Unreachable 'Count OK' levels prevent acknowledgement
| Component | BI | ||||||
| Title | BI: Unreachable 'Count OK' levels prevent acknowledgement | ||||||
| Date | Nov 10, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Compatible - no manual interaction needed | ||||||
| Checkmk versions & editions |
|
If a BI rule uses the aggregation function Count the number of nodes in
state OK and its levels require more OK nodes than the rule has child
nodes, the aggregate can never be OK. Such aggregates were never
considered acknowledged, even if all of their child nodes were
acknowledged. If you enabled the computation option Show downtime only
when all current problems are covered, they were also never considered
to be in a scheduled downtime.
Checkmk decides both by treating the acknowledged (or in downtime) child
nodes as OK and checking whether that makes the aggregate OK. Since
these aggregates never become OK, the check always failed. Checkmk now
compares against the state the aggregate has when all of its child nodes
are OK instead:
- If only the OK level is out of reach, the aggregate is at best
WARN. It is acknowledged, or in downtime, if its child nodes cover everything that makes it worse thanWARN. - If both levels are out of reach, so that the aggregate is always
CRIT, all child nodes must be acknowledged, or in downtime.
If you use the special agent rule BI aggregations with the option
State, if BI aggregate is acknowledged or State, if BI aggregate is in
scheduled downtime, the affected Aggr services may now report the
configured state instead of CRIT or WARN. You don't need to change
anything.
See Werk #22689 for a related fix of the service period and downtime of these aggregates.