ID: 2537
Title: BI Editor: restructured, now show tree structure of aggregations, show unused rules
Component: BI
Level: 2
Class: New Feature
Version: 1.2.7i3
The WATO module for BI aggregations has undergone a slight rework. Aggregations and Rules are
now show on separate pages. In the table of aggregations you now can unfold the tree of rules
(which is not the same as the final tree of items).
A new page shows all rules that are not called by any other aggregation or rule. This helps
to cleanup your configuration.
ID: 2492
Title: check_mk_agent.linux: avoid problems with crashing waitmax after Ubuntu update
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i3
Some users have reported that after an update of their Ubuntu target hosts, the command
<tt>/usr/bin/waitmax</tt>, which is shipped with the Check_MK Agent, actually segfaults
the program being run with it. This could be related to the fact that <tt>waitmax</tt>
is statically linked in order to be independent of 32/64 bits and of the libc in use.
The agent now looks if <tt>/usr/bin/timeout</tt> exists and prefers that over <tt>waitmax</tt>.
<tt>timeout</tt> has been introduced in the coreutils version 8+. It is missing e.g.
on RedHat 5.X, so <tt>waitmax</tt> is still needed for a couple of years...
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.