ID: 6498
Title: fileinfo.groups: Conjunctions of different levels are configurable
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
File group statistics such as
<ul>
<li>count</li>
<li>size</li>
<li>largest size</li>
<li>smallest size</li>
<li>oldest age</li>
<li>newest age</li>
</ul>
can be checked by upper and lower thresholds which consists of two values: warn
and crit. These levels are independent of each other.
In order to check dependent file group statistics you can configure
conjunctions of single levels now. A conjunction consists of a monitoring state
and any number of upper or lower levels. If all of the configured levels within
a conjunction are reached then the related state is reported.
ID: 6664
Title: WATO notification rules configuration: expansion of condition elements did not work for user rules
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
ID: 6801
Title: fortigate_ipsecvpn: Tunnels which are down or ignored are listed in the long output
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
ID: 6778
Title: Additional fix for URL redirect from /[site]/ to /[site]/check_mk/
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.6.0i1
The werk #6773 changed the behaviour of the URL redirect from <tt>/[site]/</tt> or <tt>/[site]</tt>
to <tt>/[site]/check_mk/</tt>. The change tried to respect custom ports but was breaking some
specific reverse proxy setups.
We have now again changed this setting to completely ignore the protocl, host and port when producing the
redirect answer which makes the client responsible for adding the correct protocol, host and port.
ID: 6644
Title: UPS output load WATO rules
Component: WATO
Level: 1
Class: New feature
Version: 1.6.0i1
UPS output load includes default levels for warn and crit levels. This
threshold levels are now configurable in WATO
ID: 6776
Title: Timeperiod ical import: Fixed limitation to 100 events per multiple day event
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
When a single repeating event creates events for more than 100 days, only the first
100 events were used by the import. This limitation has now been removed.
ID: 6412
Title: mk_docker_container_piggybacked: don't try to execute the check_mk_agent inside a container if no bash is available
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
If bash is not available in a docker container docker reports the error on stdout.
The mk_docker_container_piggybacked plugin misinterpreted the error as an
available check_mk_agent inside of the container.
Affected hosts using the mk_docker_container_piggybacked plugin have to update
the plugin to the new version to avoid this behaviour.
ID: 6515
Title: Dropped libmcrypt / php-mcrypt dependency
Component: Site Management
Level: 1
Class: New feature
Version: 1.6.0i1
The libmcrypt library and the mcrypt php module is not necessary for Check_MK
and it's major components. We drop it because it is the last dependency on
RedHat distros that is fetched from the EPEL repositories. This means that we
can now skip this step during initial installation and thus simplify the
installation process on these systems a bit more.
The only component left that uses libmcrypt is the fairly old NSCA receiver
which is still shipped with Check_MK. We keep this component for the moment
since it's used by several installations and we currently have no 1:1
replacement for it. In case you need to use NSCAs encryption, which is highly
recommended when you use NSCA, you may have to install libmcrypt by hand to
make it work.
ID: 6188
Title: Dropped fping dependency (Removes check_fping)
Component: Other Components
Level: 1
Class: Bug fix
Version: 1.6.0i1
The external fping package dependency has been removed from Check_MK. It is
a utility to send "fast pings". The active check "check_fping" needs this
package to work.
In Check_MK it is standard and recommended to use "check_icmp" for pinging
hosts using ICMP. It is used for the host checks of the Raw Edition and for
the active checks named "PING". The Microcore uses it's smart ping feature
for the host checks by default and falls back to "check_icmp" in some
situations.
The check check_fping is not used by default. In case you used it, it is
recommended to use one of the options mentioned above. If this is no option
for you for some reason, please let us know.