ID: 0970
Title: liveproxyd: handle situations with more then 1024 open files
Component: Livestatus-Proxy
Level: 2
Class: Bug Fix
Version: 1.2.5i3
When you are using the Livestatus Proxy Daemon for connecting lots
of sites and you have lots of concurrent users then two things could
happen:
1. You might run out of files. The reason is that per default on most
Linux systems the number of files a process is allowed to keep open
is limited to 1024. The can be increased by using <tt>/etc/security/limits.conf</tt>.
The script launching the <tt>liveproxyd</tt> need to issue a <tt>ulimit -S -n unlimited</tt>
before starting. In the OMD builds of the Check_MK Monitoring System this
has been added for recent development builds. The <tt>liveproxyd</tt> now handles
this situation better and does not long run into a busy CPU loop. It waits for
5 seconds and restarts itself instead.
2. Even if you increased the number of allowed open files the <tt>liveproxyd</tt>
could never open more than 1024 files on most Python versions (due to a limit of
the system call <tt>select()</tt>. This has been fixed by using the <tt>poll()</tt>
system call.
ID: 0610
Title: mk_inventory: windows inventory check now included, install date added to data
Component: HW/SW-Inventory
Level: 2
Class: New Feature
Version: 1.2.5i3
ID: 0968
Title: Notification plugins now configurable via WATO
Component: Notifications
Level: 2
Class: New Feature
Version: 1.2.5i3
Check_MK now has a new alternative API for notification script, which allows
them to be configured via WATO. The classical API provided the possibility of
a list of strings that was passed to the script as <tt>PARAMETER_1</tt>,
<tt>PARAMETER_2</tt>, etc. The new API passes arguments according
to keys in a configured dictionary, like <tt>PARAMETER_FROM</tt> and
<tt>PARAMETER_REPLY_TO</tt>.
Two notification scripts have been converted to use the new API: <tt>mail</tt>
(sending HTML emails) and <tt>mkeventd</tt> (forwarding to the Event Console).
The configuration of a notification script does only work with the new
<i>Rule Based Notifications</i> can be done at two places:
<ul>
<li>In new rulesets below <i>Host & Service Parameters</i> → <i>Monitoring Configuration</i> → <i>Notifications</i></li>
<li>Right in a notification rule</li>
</ul>
Both configurations are being merged on a per-key basis. That way you
can e.g. setup a <tt>From:</tt> header for your outgoing emails via
a global rule, but select various different <tt>Reply-To:</tt> addresses
in different notification rules.
If a configuration key appears both in <i>Host & Service Parameters</i> and
in a notification rule then the latter one has precedence.
ID: 0965
Title: Cumulative permissions and contact groups for WATO folders
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.5i3
WATO folders have now two new checkboxes in the <i>Permissions</i> attributes:
<ul>
<li><i>Give these groups also permission on all subfolders</i></li>
<li><i>Add these groups as contacts in all subfolders</i></li>
</ul>
The first one will add the configured groups of a folder also as permitted
groups to all subfolders (recursively). The second one will add the configured
groups as <b>contact groups</b> to the hosts in all subfolders.
The idea behind that is a simplification of the configuration. It is now
sufficient to specify the groups of you more general administrators at
the top of the folder tree and add more and more specific groups at
the lower levels of your folder tree.
In the table of hosts you now will see the permitted groups and the
contact groups of a host as two separate columns.
ID: 0964
Title: Fix hanging shutdown of CMC on RedHat 5.X
Component: Notifications
Level: 2
Class: Bug Fix
Version: 1.2.5i3
When using the CMC on RedHat/CentOS 5.X then the CMC would not correctly
shutdown. The reason is, that the Python implementation of that OSes
raises an Exception on sys.exit, while newer versions don't. This has
been fixed by handling <tt>SystemExit</tt> explicitely.
ID: 0963
Title: New snapin with virtual host trees
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.5i3
We have added a new snapin to Multisite: <i>Virtual Host Tree</i>. This snapin allows you to
have trees of your hosts created based upon tags. In order to use this simply add the snapin
to your sidebar and go to the <i>Global Settings</i>, section <i>Status GUI (Multisite)</i>
and the new setting <i>Virtual Host Trees</i>.
You can create an arbitrary number of virtual trees. They will be globally visible for
all users. Each tree consists of a sequence of tag groups. Let's assume that you have
created a virtual tree from the three fictive tag groups <i>Location</i>, <i>Application</i>
and <i>Criticality</i>. The virtual host tree will then have tree levels. At the
top level there is the selection of the location, on the second level the application
and on the leaf-level the criticality.
A click of an arbitrary node of the tree brings you to all hosts having the selected
tags.
ID: 0900
Title: notify_multitech.py: new treasures script for notifying via MultiTech SMS Gateway
Component: Notifications
Level: 2
Class: New Feature
Version: 1.2.5i3
donated by Stadt Regensburg
ID: 0899
Title: enterasys_temp: New Check for temperature sensor in Enterasys Switches
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i3