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".
ID: 5244
Title: Activate Changes: Fixed "Has never been activated" status message
Component: WATO
Level: 1
Class: Bug fix
Version: 1.5.0i1
This message was shown, because some state files were only stored temporarily.
ID: 5478
Title: fileinfo: fix globbing pattern expansion
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
Fixes the issue that globbing patterns were not expanded
after the introduction of werk 5344.
ID: 5130
Title: cmcii: New check to monitor Rittal CMC-II devices.
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i1
This check monitors the overall status and configuration of Rittal CMC-II
devices as well as the status of attached units.
ID: 5227
Title: Checkgroup humidity: Fix swapped lower levels and definition of only one kind of levels
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
Previously, all checks of the checkgroup humidity would crash if only lower or only upper levels
were configured. Lower levels configured in the GUI would be swapped in the check, ie the
warn level would be interpreted as the crit level and vice versa. This has been fixed.
ID: 5459
Title: Disallow group-related wait objects, avoiding crashes
Component: Livestatus
Level: 1
Class: Bug fix
Version: 1.5.0i1
Using wait objects on some tables (hostsbygroup, servicesbygroup,
servicesbyhostgroup) doesn't really make sense: Hosts and services can be
part of many groups, so we would have to conjure up a random group out of
thin air. Consequently, we forbid wait objects on these tables now.
Previously, the monitoring core crashed when we would try to wait on such an
object, anyway.
ID: 5458
Title: Enable filtering on columns with macros when the Nagios core is used
Component: Livestatus
Level: 1
Class: Bug fix
Version: 1.5.0i1
Some host/service columns (check_command, notes, notes_url, action_url,
icon_image) can contain macros, and they have a corresponding "..._expanded"
column with those macros already expanded. Previously, it was not possible
to use filters on those expanded columns when the Nagios core was used.
This has been fixed.