ID: 2897
Title: Changed move host action to be an action icon using a popup menu
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.7i4
The "move host" action in the host configuration lists has been changed to be
an action icon just like the other host actions.
When you have a confiuration with a large folder hierarchy like hundrets of
folders, this change will increase the rendering time of the hosts lists a
lot.
ID: 2879
Title: WATO-Replication of MKPs and files in the local/ hierarchy
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.7i4
Distributed WATO now offers a new checkbox <i>Replicate extensions (MKPs and
files in ~/local/)</i> in the settings of a site. When you check this then
all MKP extension packages and files below the <tt>~/local/</tt> filesystem
on the site will be replicated to the slaves. Note: existing files and MKPs
on the slave will be removed, so you have an exact replication.
Extension replication is activated per default now if you create a new
site connection. Your existing connections are not touched so this is a
compatible change.
Extension replication only works with CEE and CRE. Manual setups
(<tt>./setup.sh</tt>) are not supported.
ID: 2779
Title: Fix moving of folders
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.7i4
This fixes the error message <i>Cannot move folder: A folder with this name
already exists in the target folder.</i>
ID: 2878
Title: Rework of host search in WATO - allow all bulk operations on search results
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.7i4
The <i>Search</i> functionality in WATO has been completely reworked. The search
results are now displayed just like a folder. All single-host and bulk operations
are now possible on the search result. You can edit, delete and move the found
hosts (or some hereof), can cleanup attributes, do discovery and even can do
parent scan.
ID: 2894
Title: Fixed broken cluster checks when using Nagios core
Component: Core & Setup
Level: 2
Class: Bug Fix
Version: 1.2.7i4
When monitoring clustered hosts using Nagios as core, the Check_MK service always
resulted in an UNKNOWN state and this exception:
NameError: global name 'set_use_cachefile' is not defined
ID: 2859
Title: Check_MK Discovery/Inventory and HW/SW Inventory services are now always using caches (if available)
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i4
The Check_MK services "Check_MK Discovery", "Check_MK Inventory" and "Check_MK HW/SW Inventory" need
data from the Check_MK agent on agent based hosts. These check were contacting the agent on their own
on every execution which could lead to logwatch messages not being processed by the agent because they
were already processed by the discovery/inventory checks.
We now set these checks to use the agent cache (if available and if recent enough). This makes the
checks only contact the agent when neccessary. This should never happen when the host is being monitored
regularly because the regular monitoring ensures that the cache is available and up-to-date.
ID: 2779
Title: Fix moving of folders
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.7i4
This fixes the error message <i>Cannot move folder: A folder with this name
already exists in the target folder.</i>
ID: 2843
Title: Hanging notification scripts could prevent all other notifications
Component: Notifications
Level: 2
Class: Bug Fix
Version: 1.2.7i4
Notification scripts are assumed to finish within short time like a couple
of seconds. If a notification script takes longer or is hanging for ever,
it prevent Check_MK from sending out other notifications. So one hanging
notification could prevent all others.
This has been fixed by introducing a global notification plugin timeout.
All notification plugins which take more than 60 seconds will be killed
so that other notifications can be done again. If you need a different
timeout, you can configure it using the global setting "Notification plugin timeout".
ID: 2771
Title: Errors in Check_MK configuration do not prevent the core from being restarted anymore
Component: Core & Setup
Level: 2
Class: New Feature
Version: 1.2.7i4
This has been implemented for the CMC configuration generating mechanism some time ago.
See werk #8294 for details. This has also been implemented for installations which use
Nagios as monitoring core.
ID: 0973
Title: Renaming of hosts via WATO
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.5i3
WATO has now a new function <i>Rename Host</i>. You will find a button with that name
in the Properties of a host. It allows a renaming of an existing host. Before you
can use that feature you need to have all changes activated, so nothing is pending.
Renaming a host is a complex precedure that will not only rename the host in WATO,
but also in:
<ul>
<li>all rules from <i>Host & Service Parameters</i></li>
<li>cluster's node definitions</li>
<li>a host's parent definitions</li>
<li>Business Intelligence rules</li>
<li>notification rules (both rule based and flexible notifications)</li>
<li>internal Check_MK data like caches and performance counters</li>
<li>auto-disovered services of the host</li>
<li>logfile information of logwatch plugin</li>
<li>stored SNMP walks</li>
<li>RR databases with performance data</li>
<li>RRD updates in journal of RRD Cache</li>
<li>spool files of PNP4Nagios</li>
<li>NagVis maps</li>
<li>monitoring history entries (events and availability)</li>
<li>the current monitoring state (including ackowledgements and downtimes)</li>
</ul>
Please note that renaming of a host involves a temporary stop of the monitoring
core. This is neccessary in order to avoid situation where the old and the new
name of a host is being used at the same time.