ID: 10403
Title: Customer-user local customizations are kept during activate changes from master
Component: Multisite
Level: 1
Class: New feature
Version: 1.7.0i1
Customer-Users belong to a customer when working on the CME. They only work
on the GUI of their corresponding remote site. They are allowed to
customize their bookmarks, views, dashboards, reports, etc. These user
local configurations are now retained when receiving files from master as
changes are activated.
Non-customer-users (e.g. GLOBAL users) normally work on the central
site and thus they should be able to use their customizations when they
log into remote sites. Thus all files are synced in their case.
User notifications follow the same logic.
ID: 10881
Title: Fix possible crash when trying to save site multiple times
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
When saving a site configuration and trying to submit the form again
a second time, this could result in an error message. No information
was lost, just the result of the page is not displayed correctly
ID: 10882
Title: Fix "Customers" dashlet shown on customer sites
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
The customer sites only have information for a single customer.
It does not make sense to show the customers snapin in the main
dashboard. You can view the numbers and open the related objects
using the Tactical overview snapin.
The customer snapin is now removed automatically from the builtin
main dashboard. In case you have built a custom dashboard, it will
not be affected by this change.
ID: 11038
Title: cifsmounts: fix erroneous display of 'stale fs handle'
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
On CIFS mounts that exceeded a blocksize of 1MB the error
'stale fs handle' was shown. Now a blocksize up to 16MB
is considered valid.
ID: 10878
Title: Fix BI aggregation state export (Regression caused by #10879)
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
The export of BI aggregation tree states e.g. using calls like
<tt>check_mk/view.py?view_name=aggr_all&output_format=python</tt>)
was broken in 1.6.0p11.
ID: 10926
Title: Monitor VMKernel swap metrics on ESX Hosts
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
This check monitors swap metrics (refering to VMkernel swappin) on ESX Hosts.
The following swap metrics are displayed: mem.swapin, mem.swapout, mem.swapused.
The metrics are obtained via special agent agent_vsphere.
ID: 10125
Title: Fixed separator of SNMP trap messages
Component: Event Console
Level: 1
Class: Bug fix
Version: 1.7.0i1
The event console messages created from SNMP traps can contain a list of
OID/value pairs. These pairs were separated by " , " previously, now they
are separated by ", " (not the missing space before the comma). Although
the new behavior is more correct, it can have an impact on your configured
event console rules: If you match on the text of the messsage, the change
can make a difference, depending on the regex you use.
A portable fix is to use " ?, " to match the separator, i.e. make the first
space optional in the regex.
ID: 10603
Title: datapower plugins: now support new revision of IBM Datapower Gateway
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
ID: 10873
Title: Report headers: Improve handling of titles with dynamic lengths
Component: Reporting & Availability
Level: 2
Class: Bug fix
Version: 1.7.0i1
In previous versions of Checkmk the title of reports could only be set to a
fixed size. Especially with generic reports, like host or service reports, this
is a problem because the titles can be of different lengths and can even exceed
the width of the document.
The "One line of text" report element has now a new configuration option
"Shrink too long texts", which is disabled by default. Once you enable this
option, the text size will be estimated before adding it to the document.
In the moment the text is too long, the system tries to wrap the text and
reduce the font size at the same time. In many cases the text is inserted in
such a way that it fits. There are still cases where the text still cannot be
made to fit properly, but for the most common cases this should be a good
enough fit.
We have changed the default "host" report template to use the new setting for
the title of the page. In case your reports are based on your own template
and want to use the new option, you will have to enable the option in the
report elements of your report template.