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.
ID: 2491
Title: Allow clickable URLs in comments and downtime texts
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.7i3
When you in include an URL like <tt>http://www.mysite.de/...</tt> into the
comment of a downtime or an acknowledgment then this URL will now be replaced
with a clickable icon pointing to that link.
ID: 2487
Title: Remove dangerous <i>Factory Reset</i> button
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.7i3
We removed the button <i>Factory Reset</i> completely from WATO. This button
is dangerous. Also it does anyway just a reset of WATO - not of other data
in the site like NagVis maps etc. For a real reset better remove and recreate
the site with:
C+:
RP:omd stop mysite
RP:omd rm mysite
RP:omd create mysite
C-:
ID: 2486
Title: Remove special handling for non-distributed-setups in WATO
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.7i3
The handling of the activation of changes of single site setups was completely
different than the case where you have a distributed setup with more than one
Check_MK site. In order to simplify code, documentation and user experiance
this distinction now has been removed. A single-site setup now exactly looks
like and behaves like a distributed setup with just one site. This has no
influence on performance or security.
ID: 2485
Title: Fix Icon "BI Aggregations containing this service", also avoid BI compilation without need
Component: BI
Level: 2
Class: Bug Fix
Version: 1.2.7i3
This werk contains a fix and a speedup: The fix repairs the BI icon that is now contained in
the drop down menu rather than directly in the view. The URL where the icon pointed was broken.
The second change is a speedup: Pages that do not show BI aggregates now do now trigger BI
compilation anymore. This is delayed until the command/icon menu is being opened. Here the
BI icon needs to be displayed and hence the compilation triggered.
ID: 2484
Title: Virtual Host Tree now allows adding levels of WATO folders
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.7i3
Amongst host tag groups you now also can add levels of your WATO
folder hierarchy. This allows the creation of even more flexible
virtual host tree, that combine information from the folder tree
and from the tag groups.
ID: 2471
Title: User IDs are now allowed to contain special characters (like German umlauts)
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.7i3
Using the GUI it was not possible to create users having user IDs containing special
characters like e.g. German umlauts. But in environments where user synchronizations
with LDAP directories is used it might happen that users with sucht user IDs need
to be synchronized into Check_MK. This was in possible in earlier versions,
which lead to some kind of inconsistencies.
To have a consistent situation for all users independent of their source, Check_MK
now allows you to create users which user IDs contain special characters.
If you already have configured a LDAP synchronization and set the option
"Translate Umlauts in User-IDs" to "replace", your already synchronized users will
be left untouched for the moment. But it is recommended to set this option to
"Keep special characters" now to allow your users to use their normal user IDs for
logging in. But please note, if you change this option, your users having special
characters in user IDs are deleted and re-created with the new name during next
LDAP sync. You will need to migrate the users profile (<tt>var/check_mk/web/[user_id]</tt>)
to make them able to use their custom views, dashboards, bookmarks etc. again after
renaming.
ID: 2471
Title: User IDs are now allowed to contain special characters (like German umlauts)
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.7i3
Using the GUI it was not possible to create users having user IDs containing special
characters like e.g. German umlauts. But in environments where user synchronizations
with LDAP directories is used it might happen that users with sucht user IDs need
to be synchronized into Check_MK. This was in possible in earlier versions,
which lead to some kind of inconsistencies.
To have a consistent situation for all users independent of their source, Check_MK
now allows you to create users which user IDs contain special characters.
If you already have configured a LDAP synchronization and set the option
"Translate Umlauts in User-IDs" to "replace", your already synchronized users will
be left untouched for the moment. But it is recommended to set this option to
"Keep special characters" now to allow your users to use their normal user IDs for
logging in. But please note, if you change this option, your users having special
characters in user IDs are deleted and re-created with the new name during next
LDAP sync. You will need to migrate the users profile (<tt>var/check_mk/web/[user_id]</tt>)
to make them able to use their custom views, dashboards, bookmarks etc. again after
renaming.
ID: 2407
Title: WATO master/slave replication: fixed problem where the configuration from the master site was not activate on slave site
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.7i3
Changes made on a distributed WATO slave site could delay a configuration update attempt from the master.
Detailed information: Any changes on a slave site which lead to a pending log entry triggered the cmcrushd.
The cmcrushd creates a configuration for the microcore, which takes precendence over creating the configuration anew.
When a snapshot got pushed from the master site, the slave site thought that there is already a precompiled configuration
available and used the cmcrushd configuration.
This problem is automatically resolved on the following configuration push from the master,
because the cmcrushd configuration is only used once.