ID: 11264
Title: Fix building agent MSI packages on SLES15SP1
Component: agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Using the Agent bakery on SLES15SP1 Checkmk servers it was not possible to
build MSI packages because the tools (msibuild, msiinfo) were missing on that
platform.
ID: 11361
Title: Reworking of discovery rulesets for network interfaces and switch ports
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
Up to now, the discovery of network interfaces and switch ports was controlled by
two main rules: "Network Interface and Switch Port Discovery" (discovery of single
interfaces) and "Network interface groups" (grouping of interfaces). With this werk,
we integrate "Network interface groups" into "Network Interface and Switch Port
Discovery" and rework the latter. The rule "Network interface groups" is now deprecated
and not applied any more.
The reworked discovery ruleset is split into three parts: the configuration of the
discovery of single interfaces, the configuration of interfaces groups and conditions
which determine to which interfaces this rule applies. In the following, we explain the
changes in more detail.
<ul>
<li>In the first part, you can activate or deactivate the discovery of single interfaces.
You can also configure the way monitored interfaces are represented, i.e., by index, by
description or by alias.</li>
<li>The second part offers the option to group interfaces. Here, you can specify the names
of the groups and they way the corresponding services display their members in the service
output (again, by index, by description or by alias). Contrary to before, there is no separate
option any more to define interface groups on clusters, since this option was anyway redundant.
</li>
<li>The third part of the rule determines to which interfaces this rule applies. You can choose
to apply this rule to all interfaces or you can set conditions such as a regular expression
matching the interface description or a set of port types. Each interface will first determine
the set of rules which actually applies to this interface and then merge these rules together,
whereby rules higher up in the hierarchy (e.g. rules in subfolders) overwrite rules further
below.</li>
<li>Note that due to the point above, this rule is a somewhat special case compared to other
rulesets in checkmk. Usually, the conditions for a rule to apply are exclusively configured in
the section "Conditions". However, here, you can set additional, interface-specific conditions,
which offer a finer control over the discovery process.</li>
</ul>
This change is incompatible. It affects the following checks:
<tt>aix_if</tt>, <tt>brocade_optical</tt>, <tt>emc_vplex_if</tt>, <tt>esx_vsphere_counters</tt>,
<tt>fritz</tt>, <tt>hitachi_hnas_fc_if</tt>, <tt>hp_msa_if</tt>, <tt>hpux_if</tt>, <tt>if</tt>,
<tt>if64</tt>, <tt>if64adm</tt>, <tt>if64_tplink</tt>, <tt>if_brocade</tt>, <tt>if_fortigate</tt>,
<tt>if_lancom</tt>, <tt>lnx_if</tt>, <tt>mcdata_fcport</tt>, <tt>netapp_api_if</tt>,
<tt>statgrab_net</tt>, <tt>ucs_bladecenter_if</tt>, <tt>vms_if</tt>, <tt>winperf_if</tt>.
For users monitoring interface groups, this change is definitely incompatible. They have to migrate
their current rules for grouping interfaces from the now deprecated ruleset "Network interface
groups" to the new discovery ruleset. Note that there is no option any more to discover interface
groups <i>instead of</i> the corresponding single interfaces. To reproduce this behavior, configure
your interfaces groups and switch off the discovery of single interfaces for the group members.
After migrating the grouping rules, these users have to re-discover the services of affected hosts.
For all others users monitoring network interfaces, this change might be incompatible. Generally,
any already discovered interface services will continue to work. However, depending on the user-
defined rules from the (now reworked) ruleset "Network Interface and Switch Port Discovery", some
interface services might vanish upon re-discovery or new interface services might appear. In such
cases, users have to adapt the new, reworked versions of their user-defined rules.
Finally, it is worth noting that the new ruleset offers the option to match all interfaces, which
allows for simplifying some rules. In particular, users might be able to simplify rules where all
interface port types and states are selected.
ID: 11259
Title: Fix host "Save & Test" action showing "API error" for all tests
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
The host diagnostic page was initially showing the message "API Error: The text
None is not a valid integer number." after adding or editing a host and
confirming the dialog with the "Save & Test" button.
This regression was introduced by werk #11254 in version 1.6.0p15.
You could workaround this issue by clicking the "Test" button on the page
showing that error. It will start the tests in the correct way.
ID: 11241
Title: Status of the Check_MK services: Fix unhandled 'State in case of restricted address missmatch' parameter
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Within the ruleset {{Status of the Checkmk services}} there's a parameter
{{State in case of restricted address missmatch}} where you can overwrite the
default state {{WARN}} if the {{Check_MK}} service reports
{{Unexpected allowed IP ranges}}. This option was introduced in Checkmk version
1.6.0 and not handled by the {{Check_MK}} service, ie. the configure state of
this option had no effect.
ID: 11371
Title: mk_oracle: Fixed failed login with specific credentials
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
With werk #10850 we introduced a fix for possible problems with upper and
lower case instances in 1.6.0p15. It made a match possible where the process
is lower case but the specific login variable definition in the configuration
file is upper case - or vice versa. This fix is incompatible with Bash
versions that are older than 4.0 and has been enhanced with this werk.
You need to replace the plugin only if you are running Oracle Databases
on an OS that uses an older version of Bash and you noticed a failed login
after upgrading to 1.6.0p15. Otherwise there is no need for interaction.
ID: 10785
Title: Metric History Painter can directly inherit their time range from report
Component: Reporting & Availability
Level: 1
Class: New feature
Version: 1.7.0i1
When configuring a Metric History column on a view on your report
additional to the predefined fixed time ranges it is now possible to
inherit from the report time range.
ID: 11400
Title: Linux agent service: IP Access List support for systemd
Component: agents
Level: 1
Class: New feature
Version: 1.7.0i1
Previously, an IP restriction for the access to the Checkmk agent, as configured in
WATO ruleset "Allowed agent access via IP address", could only be realized with the
help of an "only_from" entry at the xinetd service that is shipped with a baked
agent package.
With this Werk, the restriction is also realizable via "IP Access Lists" for the
Checkmk agent systemd service/socket. Depending on the configuration of the
"Checkmk agent network service" WATO ruleset, a configured IP restriction will be
realized activating either the systemd service/socket, or the xinetd service, with
the systemd service/socket being the default.
There is no action needed to activate this new behavior.
The benefit of this change is, that you won't need to install xinetd any more to
realize an IP restriction, but can rely on systemd, that is standard on most Linux
distributions.
<b>Note</b>: The feature "IP Access Lists" is supported by systemd versions >= 235
only. The agent installation will check for a sufficient version and prevent the
systemd service/socket from being activated, if the check fails. Depending on the
"Checkmk agent network service" configuration, the installation will try to fall
back to the xinetd service, see also Werk #10431.
ID: 11342
Title: postgres_instances: Set status to CRIT in case no instance is running
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
ID: 11304
Title: mysql.connections: extended plugin to show currently open connections in addition to maximum parallel connections
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The plugin mysql.connections shows the maximum number of parallel connections
since the server was started in relation to the maximum number of parallel
connections allowed. We have extended this plugin to include the number of
currently open connections to the server. This value is shown by the MySQL
status variable 'Threads_connected'.