ID: 4229
Title: New Web GUI logging configuration
Component: Multisite
Level: 1
Class: New Feature
Version: 1.4.0i4
The logging mechanism of the Web GUI has been changed to a single
global setting. Similar to the new core log level configuration.
Existing verbose log level configurations will be reset to the
default log level during update.
ID: 4227
Title: New manual WATO configuration lock mechanism
Component: WATO
Level: 2
Class: New Feature
Version: 1.4.0i4
It is now possible to manually lock the WATO configuration for modifications and set
the configuration to read only mode.
You can find the option to configure it below <i>Global Settings > Read only mode</i>.
On that page the WATO configuration can be set to read only mode for all users that are not
permitted to ignore the read only mode. All users that are permitted to set the read only mode
can disable it again when another permitted user enabled it before.
The read only mode can be set permanently or in a specific time window. You can set a message
which is then shown to all users while the read only mode is active.
ID: 4184
Title: hivemanager_devices: Fixed bug if device is up for more than 1 year
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.4.0i4
The checkplugin does not crash anymore if a device is up for more than 1 year.
ID: 4009
Title: Business intelligence: Multihost aggregations are no longer broken after a core restart
Component: BI
Level: 1
Class: Bug Fix
Version: 1.4.0i4
ID: 4183
Title: ibm_imm_fan: Fixed crash if fan speed is "unavailable"
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.4.0i4
If the value for speed is "unavailable" the behaviour is now similar to
"offline": The state becomes CRIT and the status detail shows the output "is unvailable".
ID: 4202
Title: Availability now avoids pending states for times before new hosts or services were added
Component: BI
Level: 1
Class: Bug Fix
Version: 1.4.0i4
When computing the availability of a BI aggregation for a time range during
which new hosts or services were added to the monitoring the state of these
objects would be displayed as (PEND) before point of time they were added. But
this is not correct. These objects where not pending but simply not yet
existing and thus not contained in the aggregation tree at all at that time.
When computing a BI state it is a big difference if something is pending
or simply not existing. One pending node can make the total tree state also
(PEND). While this is correct in the current monitoring it breaks the
availability computation.
BI availability has now been fixed so that unmonitored hosts and services
are correctly being removed from the tree in the according time ranges and
the real state at that time is reconstructed. That way bogus (PEND) phases
of BI aggregations are being avoided.