ID: 12067
Title: Fix rowselections written to null.mk file
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
Different pages, e.g. the "BI aggregations" page, wrote a "null.mk" file on row
selection.
>From now on the filename will be the selection ID and the content will have the
regarding key of the respective page.
ID: 12008
Title: Autodiscovery: Drop scanning configuration option
Component: Setup
Level: 1
Class: New feature
Version: 2.1.0i1
In the rule "Periodic service discovery" users have been able to configure either
"Perform full SNMP scan always, detect new check types" or
"Just rely on existing check files, detect new items only".
This was solving performance issues since the automatic service discovery was not
using cached data.
Since this has been fixed, this option is no longer required. User will now always
detect new check types.
ID: 12130
Title: Raw Edition: Fix graph in HTML notifications
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.1.0i1
The HTML mail notifications of the Raw Edition were not containing graph images
anymore.
ID: 11785
Title: Show device mapping for Lancom routers
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
Lancom routers may map physical to logical devices which has not been taken
into account when checking Lancom network interfaces.
This change will add this mapping information to the check output.
ID: 12065
Title: Fix word wrap on service discovery page
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
If long service names contained no spaces, the service name was further
written into the status detail column.
The name will now be wrapped correctly.
ID: 11631
Title: License usage report: How to exclude sites, hosts and services from license counting
Component: Setup
Level: 1
Class: New feature
Version: 2.1.0i1
The license usage report should NOT contain sites, hosts and services which are
used for test scenarios. Due to a lot of different scenarios we need a
flexible way for excluding these test scenarios from the reports.
Let's begin at atom level. A service can be excluded by adding the label
{cmk/licensing:excluded}. For example you can do that via the ruleset
{Setup > Services > Service monitoring rules > Service labels}.
In order to exclude a host and all it's services you only have to label this
host with {cmk/licensing:excluded}. In this case you do not need additional
labels for the host services. Adding a host label can be achieved with the
ruleset {Setup > Hosts > Host monitoring rules > Host labels}.
If you want to exclude a whole site you can use the host label ruleset
{Setup > Hosts > Host monitoring rules > Host labels} for ALL hosts.
Thus, the idea is the following: if a higher level entity (eg. a host) is
already excluded then the lower level entities (eg. host services) do not have
to be excluded again. This also may reduce the number of rulesets.
ID: 12127
Title: Fix one site logging out the login session of another site
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
Since #11499 we are tracking login sessions in each site individually.
This results in one change of the authentication session handling that
has not been mentioned in the previous werk before.
In previous Checkmk versions it was possible to share login session between
Checkmk sites of a single distributed setup. You could login into the central
site and then browse to the user interface of the remote site and did not have
to login into that site because your central site login session was accepted.
This is not possible anymore.
The result is: The login sessions of Checkmk sites are now completely
independent of other sites.
ID: 12128
Title: Fix random encrypted livestatus connection issues without Livestatus proxy
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
When using encrypted livestatus connections for accessing remote sites while
not using the livestatus proxy daemon, this could result in errors like
"attempt to connect already-connected SSLsocket" or some handshake related
errors like "The handshake operation timed out".
This was caused by the livestatus.py client which tries to optimize the connect
timeouts by first starting with a very small timeout and then retrying with a
larger timeout value. This worked as expected for not encrypted connections,
but not for encrypted connections which were able to perform the connect but
not the TLS handshake in time. The second try was then failing because of the
already connected socket from the first try. This already connected socket is
now handled correctly and will retry the handshake with a longer timeout.
ID: 12047
Title: Availability: Fix displaying of availability popup after validation error
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
When an availability option form is submitted and a validation error occurs,
the form is now displayed on page load to visualize the error to the user.