ID: 0595
Title: dell_chassis_power, dell_chassis_powersupplies: new checks for Dell Poweredge Chassis Ppower consumption
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i1
These checks measure the overall power consumption of the chassis of the Dell Poweredge Blade Server
as well as the power consumption of the individual blade nodes as given by the Dell Chassis Management
Controller (CMC)
ID: 0749
Title: Allow to restrict visibility of events by their host contacts
Component: Event Console
Level: 2
Class: New Feature
Version: 1.2.5i1
The Event Console has now two new permissions:
<ol>
<li>See all events</li>
<li>See events not related to a known host</li>
</ol>
Both permissions default to <i>yes</i> in all roles. If you remove the <i>See all events</i>
permission then a user can only see events for hosts that either he is a monitoring contact for
or that are not known to the monitoring at all (i.e. no host with such a name or IP address
is configured as monitored host in your monitoring core). The visibility of the later
ones can be switched off with the second permission. The second permission is only relevant
if <i>See all events</i> is set to <i>no</i> - of course.
Furthermore you can now assign <i>Fallback Contact Groups</i> to an event. This
is done with a new rule option in the section <i>Outcome & Action</i>. As
soon as you assign contact groups these will be assumed for all hosts
that are not in the monitoring. That groups will be attached as an additional information
to each event created with that rule. These events will then be handled like as if the
host is known to the monitoring when it comes to the visibility.
ID: 0748
Title: Also custom views now have permissions
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.5i1
In that past only builtin views had permissions that you could disable in a
role and that way remove those views for certain users. Now this also works
for custom views - i.e. views that a user has created with a new unique name
and and that is published for other users.
Please note that regardless of a view's permission the owner of the view can
always see it. If you do not like this you can remove the permission for
creating custom views.
The default for new views is still that all roles have the permission for
this view.
ID: 0748
Title: Also custom views now have permissions
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.5i1
In that past only builtin views had permissions that you could disable in a
role and that way remove those views for certain users. Now this also works
for custom views - i.e. views that a user has created with a new unique name
and and that is published for other users.
Please note that regardless of a view's permission the owner of the view can
always see it. If you do not like this you can remove the permission for
creating custom views.
ID: 0715
Title: BI aggregates now acknowledgement information
Component: BI
Level: 2
Class: New Feature
Version: 1.2.5i1
Check_MK BI now also aggregates the information wether problems that make the aggregate
non-OK are acknowledged. Please refer to the updated <a href="checkmk_bi.html">documentation
about BI</a> for details.
ID: 0714
Title: BI aggregations now also honor scheduled downtimes
Component: BI
Level: 2
Class: New Feature
Version: 1.2.5i1
A BI aggregate now also aggregates the additional information wether it is
in a scheduled downtime or not. Please refer to the updated <a href="checkmk_bi.html">documentation
about BI</a> for details.
ID: 0590
Title: mkeventd: fixed encoding of unicode characters in the snmptrap receiver
Component: Event Console
Level: 2
Class: Bug Fix
Version: 1.2.5i1
Messages coming in via the build-in snmptrap receiver and containing unicode characters
never matched any rule because the matching algorithm threw an exception. This
has been fixed.
ID: 0721
Title: Use hard states in BI aggregates
Component: BI
Level: 2
Class: New Feature
Version: 1.2.5i1
Check_MK BI is now able to base the computation of the state of an BI aggregate
on hard states of hosts and services. This is a new option at the top level
of a BI aggregate. In WATO this is a new check box in each aggregation called
<i>Base state computation on hard states</i>.
When you edit your BI aggregates with a text editor then simply prefix
your aggregation entries with the keyword <tt>HARD_STATES</tt>. Here
is an example:
F+:etc/check_mk/multisite.d/mybi.mk
host_aggregations += [
( HARD_STATES, 'Hosts', FOREACH_HOST, ['tcp'], ALL_HOSTS, 'host', ['$1$']),
]
F-:
<b>Note</b>: Please make sure that all of your monitoring sites are
updated to the same Check_MK version as your Multisite server. This new
BI features needs an up-to-date Livestatus implementation.
ID: 0713
Title: New bulk notifications
Component: Notifications
Level: 3
Class: New Feature
Version: 1.2.5i1
The new rule based notifications now also support a new feature called <i>Bulk Notifications</i>. The
idea is to send multiple notifications, that are created within a short time frame, within one email and
not as separate emails. This can help in situations where due to some general problem dozends of
notifications would happen in a sort time. Also it can be used in order to create something similar
to mailing list digests: you can get informed about all problems once a day. Please refer to the
<a href="http://mathias-kettner.com/checkmk_rbn.html">online documentation</a> for details.