ID: 4002
Title: BI: Major Rework of Code. Apache processes now share computated data
Component: BI
Level: 2
Class: New Feature
Version: 1.4.0i3
Previously, each apache process had to compile the all BI aggregation trees by itself.
This generated lots of CPU load during core restart, especially on larger BI configurations.
With this update, an apache process no longer computes the BI trees only for personal usage.
The computation results are now shared between the different processes through cache files.
If you encounter any bugs with this new mechanism you can switch back to the old
implementation via the global settings option <i>Use legacy compilation for BI aggregations (slower)</i>.
ID: 4151
Title: Use notification fallback also for hosts not known to the monitoring
Component: Event Console
Level: 2
Class: New Feature
Version: 1.4.0i3
This can happen if you forward notifications from the Event Console. All
contacts that are configured for notifications fallback and also the
global fallback email address will be regarded as contacts in that
case.
ID: 4149
Title: Fix notifications from Event Console if host has more than one contact
Component: Event Console
Level: 2
Class: Bug Fix
Version: 1.4.0i3
Notifications from the Event Console would never be sent if the
contact information had to be fetched from the host (not coded in
the rule itself) and the host had more than one contact.
ID: 4000
Title: Windows Agent: fixed broken mrpe section
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.4.0i3
This section did actually never work in 1.4.0 since the output formatting was broken...
ID: 4116
Title: mk_oracle.ps1: added Oracle wallet support to Windows plugin
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.4.0i3
The plugin for windows could be used with the Oracle wallet. The support is
limitted to all Instances except ASM. This function is only for
administrators who really knows how to use the wallet.
You have to add an entry with the name of the instance. Please check the
connection with SQLPlus before trying to use the plugin.
The plugin use the following connection:
sqlplus /@<ORACLE_SID>
You have to add a credential to the wallet with the ORACLE_SID as name for
the entry:
Example:
mkstore -wrl <Wallet Directory> createCredential „<ORACLE_SID>" <Username> <Password>
The wallet is only used, when username is set to '/'. Password,
hostname and listener-port is ignored, because the tnsnames.ora is used.
Please read the doumentation from Oracle for using the wallet. The
sqlnet.ora must be configured for your environment and the wallet must be
created before adding some entries. You could use TNS_ADMIN in
mk_oracle_cfg.ps1 for pointing to the sqlnet configuration for the plugin.
ID: 3994
Title: windows agent: fixed memory and file handle leak when using windows eventlog
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.4.0i3
The windows agent did never close any dll files it opened...
ID: 4075
Title: Activate Changes has been reworked
Component: WATO
Level: 2
Class: New Feature
Version: 1.4.0i3
The activate changes dialog of WATO has been reworked to improve several things:
<ul>
<li>It is now possible to add a comment during an activation. This optional comment
is written to the audit log and can be used to document the logical reason for
the changes you have made.</li>
<li>Several activations can now run in parallel while they not affect the same site.
This means that on each site one activation can be executed at the same time.</li>
<li>Pending changes are now correctly acknowledged. In previous version when you started
an activating, made a change during the run, the run acknowledged this just created
change even if it has not been activated by the just finished activation run.</li>
<li>Pending changes are now tracked for each site individually. Previous version only
knew whether or not a change has been activated on <i>all</i> sites.</li>
<li>Fixed locking problems during activation leading to possible issues when multiple
users execute activations in parallel.</li>
<li>You can now select a custom collection of sites and activate them in a bulk.</li>
</ul>
ID: 3651
Title: Fixed potential segfault with Nagios core when accessing log/commands table via Livestatus.
Component: Livestatus
Level: 2
Class: Bug Fix
Version: 1.4.0i3
Under rare circumstances, the Nagios core could crash when the "log" or
"commands" table was queried via Livestatus. Sites using the Micro Core
were not affected by this bug.