ID: 5532
Title: Host/Service states and outputs can now be translated
Component: cmc
Level: 2
Class: New feature
Version: 1.5.0i2
The states and service status detail of hosts and services can now be translated. You can now
use the rules {{Host state translation}} and {{Service state translation}} to configure the
Check_MK core to translate either specific states to other states or the status detail to other
texts.
States: For each host/service you can configure a transformation of each possible monitoring state
to another one.
The state translation can, for example, be used to inverse a host check in case you want to get
a notification in case a host becomes reachable.
The translation of detail outputs is done using regular expressions. You can specify multiple
regular expressions (infix match, case sensitive) per object which are applied to the current
status detail. The matched text will be replaced by the specified replacement text. You can
use match groups to extract parts of the original text using the regular expression.
ID: 5548
Title: zpool_status: Fixed crash if pool has been deleted or vanished
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
The service would crash if a previously detected pool has been removed/deleted
or vanished for some reasons. This is now fixed and the service output will
reflect that no pool is available.
ID: 5531
Title: New WATO page "Best practices" can be used to find things to improve in your Check_MK
Component: WATO
Level: 2
Class: New feature
Version: 1.5.0i1
The new WATO page "Best practices" is meant to give you hints about your Check_MK installation
and the things you could improve in terms of performance, reliabilty and security.
In the moment you open the page, it starts analyzing your Check_MK installation and executes
different tests. Test may detect that a thing is OK and report the test to be OK. Other
tests may result in WARN state in case you could be interested in changing something.
Other tests may report a CRIT state in case we think that you have a critical situation which
should be fixed for a completely working Check_MK setup.
Please note that this feature and the implemented tests are still in an early phase of
development. Understand the test results as pointer on things you should check.
Each of the tests can be acknowledged just for a single site or all your sites. In case you
came to the decision that a reported problem is not really a problem for you, you can
acknowledge the test results.
In case you fix a problem, you won't need to acknowledge it. Just open up the page again,
which should then turn your test into OK.
ID: 5529
Title: Fixed accidentially cloning own visuals instead of builtin visuals
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.5.0i1
It could happen that one wanted to clone a builtin visual (e.g. dashboard)
but was cloning his own visual instead.
This could happen if the user already has a visual with the exact name like
the visual he tried to clone.
ID: 5530
Title: Clicking on "Edit dashboard" accidentially copied dashboards with "publish to others"
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.5.0i1
When one clicks on "Edit dashboard" to edit the currently visible dashboard and the dashboard
is not owned by this user, the dashboard is cloned in the context of the current user. This
is intended and equal to, for example, the views.
What was unintended is the fact that the "public" flag of the cloned dashboards was not forced
to be forced. This way all users (with enough permissions) were publishing their cloned views
leading to strang situations where from time to time a user could see different dashboards.
The "Make this dashboard available for other users" is forced to be unchecked. This way a user
clones the dashboard for himself in the first place.
ID: 5528
Title: Fixed showing help when executing "omd" without mode argument (1.4.0p18 regression)
Component: Site Management
Level: 1
Class: Bug fix
Version: 1.5.0i1
With 1.4.0p18 the output of the help text when executing the "omd" command without argument
broke. It printed an exception instead of the help text. As workaround you can execute
"omd help" to get the help text.
ID: 5518
Title: win.mem: Fix incorrect representation of absolute memory levels in graphs
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
Previously, a warn or crit level of eg. 20 GB would be displayed in the graph as 20 TB
due to the levels not being set to the same unit as the performance value itself.
The problem only affected the levels passed to the metrics system for representation,
not the actual levels used for evaluation.
ID: 5461
Title: Fixed WaitTimeout handling
Component: Livestatus
Level: 1
Class: Bug fix
Version: 1.5.0i1
The WaitTimeout given in a Livestatus query was handled incorrectly: It was
applied each time the condition was not true, and not for the whole query.
This has been fixed.
ID: 5262
Title: Fix bug in agent bakery (regression #5261, since 1.4.0p17)
Component: agents
Level: 2
Class: Bug fix
Version: 1.5.0i1
Werk #5261 introduced a bug that made it impossible to bake new agents for some specific rulesets.
This would result in error messages like the following:
<pre>
"TypeError: key ('custom', 'win_certificates/lib/local/win_certificates.ps1') is not a string"
</pre>
After an update, no further action is required.
ID: 5460
Title: Waiting without a wait condition immediately returns now
Component: Livestatus
Level: 1
Class: Bug fix
Version: 1.5.0i1
Note: This change only affects users writing their own tools for the
Livestatus interface, and only those tools which rely on an edge case.
Up to now, Livestatus had a special obscure case: Using a WaitTrigger header
in a query without a WaitCondition header resulted in waiting for the
trigger exactly once. This is a misfeature, because it is effectively
useless and doesn't do what one might expect: Due to spurious wakeups
(https://en.wikipedia.org/wiki/Spurious_wakeup), waiting might return
earlier basically at any time.
To fix this behaviour, the special case has been removed, and a missing
WaitCondition always has its expected semantics (always true) now. Note
that this is consistent with a missing Filter header, which means "no
filtering".