[checkmk-commits] Check_MK Git: check_mk: #2354 BI aggregations now also consider the service period

Module: check_mk Branch: master Commit: e716278c68d46250234ca902f58e0393cb6621f4 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=e716278c68d462… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Wed Jun 17 15:55:45 2015 +0200 #2354 BI aggregations now also consider the service period BI aggregations now also consider the service period of their contained services and hosts - just like for downtimes and acknowledgements. A BI aggregate is thus considered to be within its service period if its state would be OK under the assumption that all objects that are currently out of their service period are CRIT and the rest is OK. Or otherwise stated: If all things that are not in their service period are switched off: if the BI aggregate would get CRIT - well then it is not in its service period. Yet in other words that means that the service period of something can only cover times where all of its vital parts also are in service period. The information "within/out of service period" is now also available for the availability computations. That allows you now to base availability reporting for BI aggregates to be based on certain time periods. --- .werks/2354 | 21 ++++++++++ ChangeLog | 1 + livestatus/src/ServicelistColumn.cc | 15 +++++++ livestatus/src/ServicelistColumn.h | 2 + web/htdocs/availability.py | 8 ++-- web/htdocs/bi.py | 77 +++++++++++++++++++++++------------ web/plugins/views/bi.py | 6 ++- 7 files changed, 99 insertions(+), 31 deletions(-) Diff: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commitdiff;h=e716278c68…