ID: 1410
Title: Output log text of scheduled downtime log entries
Component: Multisite
Level: 1
Class: New Feature
Version: 1.2.5i6
Multisite now shows the text that is attached to a scheduled downtime start/stop in the
monitoring logfile when showing the history of a host or service. Alas, Nagios does not
log anything useful in those entries. The Check_MK Micro Core logs the downtime comment,
which is by that way now visible in the historic views of Multisite.
ID: 1121
Title: Rule based notifications formular: No longer raises Request-Uri-Too-Large errors
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.5i6
If you wanted to create/edit a rule based notifcation and the formular itself had too much
configurable host tags, contact groups, etc. there was a problem on sending this formular to the server.
The data was sent with a GET request, which only allowed a limited url length.
This formular is now sent with a POST request.
ID: 1409
Title: Extended Check_MK-API: check function may return None
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i6
A check function may now return <tt>None</tt> (or simply end without
returning anything). This will no longer create an exception but return
state <tt>UNKNOWN</tt> and - depending on the type of the check -
one of the following outputs:
<tt>Item not found in SNMP data</tt>
<tt>Item not found in agent output</tt>
This means that for the typical check that loops through the agent
output looking for its item now does not need to manually do a
C+:
return 3, "Something not found in agent output"
C-:
anymore. This is now the default case. This has several advantages:
<ul>
<li>You save some code in the check implementation.</li>
<li>The output of the various checks is unified.</li>
<li>A future Check_MK version can easily have a rule for changing the state
in such cases from UNKNOWN to WARN or CRIT.</li>
</ul>
ID: 1120
Title: Multisite filters Host/Service Contactgroup: Fixed livestatus exception
Component: Multisite
Level: 2
Class: Bug Fix
Version: 1.2.5i6
The multisite filters <tt>Host Contactgroups</tt> and <tt>Service Contactgroups</tt> were
not working because of an incorrect livestatus filter formatting.
This resulted in an livestatus exception every time any of these filters were actively used.
ID: 1408
Title: mknotifyd now really reads all configuration files below mknotifyd.d
Component: Notifications
Level: 2
Class: Bug Fix
Version: 1.2.5i6
Previously the notification spooler daemon <tt>mknotifyd</tt> just read the
single file <tt>etc/check_mk/mknotifyd.d/wato/global.mk</tt>. Now it reads
all files below <tt>etc/check_mk/mknotifyd.d</tt> - just as one would
expect. Note: there is still no <tt>etc/check_mk/mknotifyd.mk</tt> file.
ID: 1406
Title: Assume PEND in count_ok aggregations if all nodes are PEND
Component: BI
Level: 2
Class: New Feature
Version: 1.2.5i6
If you are using the BI aggregation function <tt>count_ok</tt> then nodes
with the state <tt>PEND</tt> (which essentially means unmonitored or not
present) are handled differently from now.
If <b>all</b> nodes are pending then the total state will also be pending.
If just some of the nodes are pending then they will not taken into account.
This is especially imported when doing availability computations on
BI aggregates.
ID: 1119
Title: WATO create rule: No longer raises an incorrect permission warning when creating a new rule
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.5i6
A normal monitoring user which had only permissions to a given subfolder
could not create a new rule when the rule formular was created with the
main directory as rule path.<br><br>
For example, if the user pressed "Create in folder: 'Main directory'" and
switched the actual rule folder to his subfolder afterwards.<br>
This resulted in a permission warning stating that the user has no permission to
write into the 'Main directory'.
ID: 1405
Title: Checkbox for settings downtimes on the hosts of the selected services
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.5i6
In the Multisite command box for setting downtimes on services there is now
a new checkbox called <i>Schedule downtimes on the affected hosts instead
of their services</i>. When you check this then the scheduled downtimes
are set on the hosts of the selected services rather then on the services
themselves. Note: When a host is in scheduled downtime then all its services
are considered to be in a scheduled downtime, as well. There is no need to
set a downtime on these.