ID: 10704
Title: Agent bakery: Fix rules of non-main folder matching for GENERIC agent
Component: agents
Level: 1
Class: Bug fix
Version: 1.6.0p9
The generic agent package should only be affected by agent related rules that
are assigned to the main folder. In previous 1.6 releases the GENERIC agent
was affected by rules from all folders.
ID: 10709
Title: Fix site certificate being overwritten during version update
Component: Site Management
Level: 1
Class: Bug fix
Version: 1.6.0p9
The sites SSL certificate (etc/ssl/sites/[site].pem), which is used by
encrypted livestatus communication, was replaced with a fresh certificate
during each "omd update".
When using certificates issued by the site CA, this was not an issue, because
the trust at the central site was established with the site CA. It was only an
issue when trying to replace the site certificate with a certificate signed
by an external CA.
ID: 10590
Title: esx_vsphere_vm: Check age of oldest snapshot
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Since a regression in version 1.6.0 the maximum allowed age of the *oldest* snapshot
(WATO rule parameter "Age of the oldest Snapshot") has only been checked if more than
one snapshot was present. This has been fixed.
ID: 10682
Title: Windows: Inventory correctly reports IP addresses for more than one network card
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously the inventory reported only IP address(s) of the last network card.
Now the error is fixed.
ID: 10681
Title: Bakery can configure Checkmk Windows agent service
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
Previously the service of the Checkmk Windows agent have been installed
using default Windows settings for the Windows service.
The new ruleset in Bakery <tt>Checkmk Windows agent service settings</tt>
gives the possibility to configure some parameters of the service during
installation.
At the time the Bakery can change next parameters: 'Restart on crash',
'Action on error' and 'Service start type'.
The same functionality in Raw Edition can be achieved using the Agent
configuration file.
ID: 10761
Title: redis_info.clients: New check to monitor Redis info clients section
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
With this check you can monitor Redis instances. The check gets input from
the redis-cli command "info" and the resulting "Clients" section. It outputs
the number of client connections (excluding connections from replicas), the
longest output list among current client connections, the biggest input buffer
among current client connections and the number of clients pending on a
blocking call (BLPOP, BRPOP, BRPOPLPUSH).
Needs the agent plugin "mk_redis" to be installed.
ID: 10588
Title: ps: Handling of non-ASCII characters during process discovery
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
This fixes a rare encoding related exception during process discovery.
If one of the matched groups contained a non-ASCII character and that
matched group was supposed to be formatted into the service description,
the discovery crashed.
ID: 10767
Title: Implement Forecast Graph prediction engine
Component: metrics
Level: 1
Class: New feature
Version: 1.7.0i1
To avoid the need for extenal dependencies for the Forecasting Graphs we
have reimplemented the prediction algorithm within Checkmk.
This Werk replaces Werk #7451. The {bin/install_fbprophet} script can be
used to uninstall previously installed dependencies.
ID: 10703
Title: Fix some reflected XSS issues
Component: Multisite
Level: 1
Class: Security fix
Version: 1.7.0i1
Fixed several reflected XSS issues that were possible because some webservice
responses that may contain user provided strings were not correctly encoded.
ID: 10738
Title: Store the site settings of sidebar snapins
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
Sometimes the configured site of the sidebar snapins "Micro Core Statistics",
"Server Performance" and "Event Console Performance" was not saved. As a
result the site was reset to the old value when the browser was reloaded.
This is fixed.