Module: check_mk
Branch: master
Commit: 66a1d53b913fd28ddea8757a4601a4c24107365b
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=66a1d53b913fd2…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Thu Nov 7 18:52:18 2013 +0100
New concept of service periods in availability reporting
There is now a pair of new WATO rules called <i>Service period for hosts</i>
and <i>Service period for services</i>. With these you can define a timeperiod
for a host and/or service within that object is expected to be available in
terms of availability reporting. An object that is out of its service period
is still being monitored and also notified. But in the reporting there is now
a new option box <i>Service Time</i> for handling this new information. You
have either:
<ul>
<li><i>Base report only on service times</i> - All phase out of the service period
of the object in question is not taken into account when computing percentages. It is
still visible in the timeline but grayed out. This enabled you to compute the availability
of on object just within a define time frame.</li>
<li><i>Base report only on non-service times</i> - This does quite the opposite: It
just shows the times where the object is <i>out of</i> its service time.</li>
<li><i>Include both service and non-service times</i> - This simply ignores the service
time</li>
</ul>
Please note, that any change to a timeperiod definition always affects future
times, never the past. <b>But</b>: it is possible to select an alternative
timeperiod for a host and object an rerun the reporting. If that timeperiod
aready had existed during the reporting time range then everything works
as expected.
<b>Note</b>: The service period make use of new Livestatus columns. You thus
need to update all of your monitoring nodes in order to use the availability
reporting - even if you do not use this new feature.
---
.werks/56 | 35 +++++++++++++++
ChangeLog | 15 ++++---
livestatus/src/TableHosts.cc | 8 ++--
livestatus/src/TableServices.cc | 8 ++--
livestatus/src/TableStateHistory.cc | 56 +++++++++++------------
modules/check_mk.py | 14 +++---
web/htdocs/images/ooservice.png | Bin 0 -> 222 bytes
web/htdocs/views.css | 5 ++-
web/plugins/views/availability.py | 66 +++++++++++++++++-----------
web/plugins/wato/check_mk_configuration.py | 16 +++----
10 files changed, 138 insertions(+), 85 deletions(-)
Diff: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commitdiff;h=66a1d53b91…