ID: 5397
Title: Microcore can now be configured to send UNREACHABLE notifications
Component: Core & setup
Level: 2
Class: New feature
Version: 1.5.0i1
Normally you don't want to receive UNREACHABLE notifications of hosts. Configuring
client/parent relationships between your hosts is a good idea to be able to
detect network outages. DOWN states of hosts will then be translated into UNREACHABLE,
making your view clear for the real cause (e.g. a router in DOWN state).
But there may be situations where you want to be able to receive these UNREACHABLE
notifications. This was already configurable when using the Nagios core for a long
time. For the Microcore the suppression of UNREACHABLE notifications was hard coded.
This has been changed now.
The default behaviour will not be changed. New sites or updates sites will not send
out UNREACHABLE notifications by default. To enable the new feature, you will first
have to tell the core to send out UNREACHABLE notifications.
To have a seamless transition we additionally changed these things:
<ul>
<li>A default rule that disables the UNREACHABLE notifications is being created
for new sites in the ruleset "Notified events for hosts". Whenever you want
to enable UNREACHABLE notifications, simply enable them using this rule.</li>
<li>Updated sites:
<ul>
<li>If you have configured rules for all your hosts in the
"Notified events for hosts" ruleset, the core will continue working
as configured.</li>
<li>Microcore: For hosts that have no matching rule in "Notified events for hosts",
the Microcore will <i>not send</i> out UNREACHABLE notifications.</li>
<li>Microcore: If you previously had configured a rule in "Notified events for hosts"
which enabled the UNREACHABLE notifications, this rule had no effect. It will now
be working after updating.</li>
<li>Nagios: For hosts that have no matching rule in "Notified events for hosts",
the Nagios core will <i>send</i> out UNREACHABLE notifications.</li>
</ul>
</li>
</ul>
ID: 5345
Title: mssql_backup: fix GUI error and show warn/crit values
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
Fixes an error visible in the GUI when no parameters are present
for the check. The check now also shows warn and crit values for
a backup type if it is in a warning or critical state.
ID: 5303
Title: local: Fixed missing warn/crit in graphs if upper and lower thresholds are in perfdata
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
A graph did not display warn/crit values if there has been upper and lower
thresholds in the perfdata of a local check. The cause of this has been a colon
in between these values. The upper thresholds are represented in a graph now.
ID: 5304
Title: mssql_backup: Fixed error if existing rule has been set before 1.5.0
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
In werk #4811 the ruleset for mssql_backup has been extended. Since then the
GUI would crash if a rule has been set up previously to this update. This
has been fixed now.
ID: 5094
Title: lnx_distro: Prefers /etc/os-release if available which is systemd-supported
Component: HW/SW Inventory
Level: 1
Class: New feature
Version: 1.5.0i1
ID: 5399
Title: Fixed multiple stored XSS injections in WATO dialogs
Component: WATO
Level: 1
Class: Security fix
Version: 1.5.0i1
It was possible to inject Javascript code to using configuration fields of different objects
(users, hosts, groups, roles, timeperiods).
These issues could only be triggered by authenticated users that have permissons to use WATO
and add/edit the objects mentioned above. Normally these are users with the roles admin or
users.
ID: 5260
Title: Fix presentation of mirrored areas
Component: metrics
Level: 1
Class: Bug fix
Version: 1.5.0i1
This werk fixes a bug in Check_MK metrics system:
When chosing "Mirrored Area" as a style in Graph Designer for multiple metrics, a "Mirrored Stacked" presentation got displayed instead.