ID: 4431
Title: Fixed enabling/disabling of notifications/active checks/passive checks
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.5.0i1
Changing various flags in an ad-hoc (i.e. non-rule-based) manner did not
work correctly: Changing a flag to a value different from the configurated
one worked, but trying to change it back to its configurated value had no
effect. This affected the various Enable/Disable buttons on the
host/service details pages plus the corresponding Livestatus commands
(ENABLE_HOST_CHECK etc.).
Note that 1.2.8 versions and earlier are were not affected by this bug.
ID: 4576
Title: if64, if64adm: Fixed interface speed handling, if highspeed data is not available or zero
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
ID: 4527
Title: websphere_mq_channels: Now has its own WATO ruleset
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i1
In order to separate Websphere MQ queues from channels, above
check plugin got its own WATO ruleset. This means that all
rules that have been configured for the {{MQ Channels}} services
have to be migrated to the new ruleset {{Websphere MQ Channels}}.
ID: 4552
Title: win_dhcp_pools: Fixed conversion of old type of rules (1.2.6) to new type (1.2.8)
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
If rules for this checkplugin have been set up in 1.2.6 the GUI crashed in
1.2.8 if someone wanted to modify these rules.
ID: 4533
Title: cisco_vpn_tunnel: Fixed handling if tunnel is not yet open and phase two values are not set
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i1
ID: 4467
Title: BI aggregation compilation: fixed race condition exception, also forks less processes for compilation
Component: BI
Level: 1
Class: Bug fix
Version: 1.5.0i1
The compiliation process now spawns less worker processes for the compilation, which reduces the overall CPU load.
Furthermore a race condition has been fixed, which was likely to happen when all of these conditions were true:<br>
<ul>
<li>there were several dozens BI requests per minute, e.g. from multiple web browsers</li>
<li>a distributed montitoring setup started to deploy new configurations</li>
<li>there were lots (>100) of BI aggregations configured</li>
<ul>