ID: 7334
Title: Prevent tag groups with a single choice (checkbox) and empty tag ID
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
In previous versions it was possible to create tag groups that had a single
choice (shown as checkbox) and an empty tag ID for this single choice. This
was not intended and was not usable at all. The tag management GUI and API
calls are now preventing this configuration.
ID: 7361
Title: lnx_if: Ignore docker veth* interfaces when inventorizing Linux interfaces
Component: HW/SW Inventory
Level: 1
Class: Bug fix
Version: 1.6.0i1
See Werk 5946 for detailed information. Inventorizing these docker
interface may led to superfluous inventory changes.
ID: 7333
Title: Introduce predefined conditions for rulesets
Component: WATO
Level: 2
Class: New feature
Version: 1.6.0i1
In the rule-based configuration of Check_MK ("Host & Service Parameters" and
"Manual Checks") it often happens that rules with the same conditions have to
be created in different rule chains. With a larger number of rules, this
quickly becomes confusing.
To improve this situation we have now added a feature called "Predefined
conditions". The idea is to preconfigure conditions in a central place, to
which you can later refer in the individual rule chains. A predefined condition
currently always consists of a full set of conditions (folder, tags, host
specification, service specification). A rule can either use explicit
conditions, as before, or refer to a predefined condition now.
You access the predefined conditions via a context button from the pages on
which you manage your rule chains.
ID: 7357
Title: wmi.include: Check_MK Discovery does not report 'vanished services' for WMI services if WMI timeout
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0p14
If a timeout occurs in a Windows agent section while executing WMI queries the
related services were handled as vanished services by the Check_MK Discovery
service. This may be misleading because this timeout is short-lived.
The WMI query timeouts are a known problem in Windows and can not be solved by
the Check_MK agent. Please see
https://github.com/martinlindhe/wmi_exporter/issues/89 for further information.
Now the Check_MK Discovery does not take WMI timeouts into account. Thus the
Check_MK Discovery does not report "vanished services" any more. The Check_MK
service handles services with WMI timeouts as "stale" further on.
ID: 7387
Title: apache_status: Ignore certificates from local hosts
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Previously not all cases of failing certificate verfication for
local hosts were handled correctly, which could lead to missing
data for that host.
Instead of handling all cases of invalid certificates we now
omit certificate verification for local addresses entirely.
This only affects the addresses "127.0.0.1", "[::1]", and
"localhost".
ID: 7239
Title: Service discovery: Fix creating disabled services rule for services with special characters
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
Services with e.g. "[" in their names could not be disabled using the service discovery page.
ID: 7130
Title: Fixed "Clustered services for overlapping clusters" rule while checking
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Normally each node is part of a single cluster host in Check_MK. Using the
ruleset {{Clustered services for overlapping clusters}} you can assign services
found on a node to different independent cluster hosts, so called overlapping
clusters. This was unregarded while executing clustered services checks on the
related clusters. This may result in wrong check results.
Example:
Each of the two clusters {{cluster1}} and {{cluster2}} has the nodes {{node1}}
and {{node2}}. On each node we have discovered a process {{Process ABC}}.
Within the ruleset {{Clustered services for overlapping clusters}} we assign
the service {{Process ABC}} from node {{node1}} to {{cluster1}}.
Now the service {{Process ABC}} which is assigned ot the cluster {{cluster1}}
processes the data of both nodes and may return a wrong check result in the
moment where {{node1}} AND {{node2}} have data for {{Process ABC}}.