ID: 12216
Title: agent_vsphere: Fix compatibility for version 5.5
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The connection to an ESX with version 5.5 resulted in the error
"Cannot login to vSphere Server (reason: [200] OK). Please check the
credentials." even if the credentials were correct.
ID: 11851
Title: Windows agent MSI checks that Windows OS is appropriate for installation
Component: Setup
Level: 2
Class: New feature
Version: 2.1.0i1
Previously, it was possible to configure the Windows agent in WATO in such
a way that installing on older operating systems would cause the Windows
agent updater to fail( or make such plugins as mk_jolokia or mk_logwatch more
inoperable). For example: setting of the <tt>Standard python environment(3.8+ )</tt>
and deploy such MSI on Windows 2008. This could cause complete falling out of the
host of the monitoring, because the installed standard Python, 3.8+, can't work
on Windows 2008.
With this release the problem has been solved. If during deployment configuration
is not supported by Windows OS, the installation will not be performed: the
MSI will always check Windows version and stops own installation if, Windows OS
doesn't match to MSI requirements. The host will continue to operates normally in
any case.
Nevertheless, you need to fix the configuration in WATO in the order to make
the update for older Windows system. In the case of the aforementioned example,
you have to select <tt>Deploy legacy environment (Python 3.4 + standard set of modules)</tt>
in the rule <tt>Install Python runtime environment</tt>, activate changes and bake
the agent.
ID: 12050
Title: Consolidation of interface check plugins
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
A lot of interface checks did exactly the same thing. The new check API allows us to
consolidate them into one check plugin {{interfaces}}, without affecting the user.
The following check plugins will be replaced by the new one:
{{statgrab_net}}, {{emc_vplex_if}}, {{vms_if}}, {{if_brocade}}, {{if_lancom}},
{{ucs_bladecenter_if}}, {{aix_if}}, {{if}}, {{if_fortigate}}, {{hp_msa_if}}, {{if64_tplink}}.
The transition to the new services is done during `cmk-update-config`.
Existing rules will apply as before, no metrics will be lost.
It may slightly change the "Service check command" count of the {{site_objects_counts}}
plugin, depending on its configuration.
ID: 12145
Title: Config update: Site specific global settings are now also updated
Component: Setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
During update from previous versions to Checkmk 2.0 some old global
configuration settings are rewritten. This is now also done in the site
specific global settings automatically during "omd update".
ID: 12144
Title: Number of fetchers is now initialized with previous Checkmk helpers
Component: Setup
Level: 1
Class: New feature
Version: 2.1.0i1
For a better compatibility of sites being updated from previous version to 2.0,
we now use the previous setting of "Maximum concurrent Checkmk checks" to
initialize the "Maximum concurrent Checkmk fetchers".
ID: 11979
Title: apache_status: HTTPS support for Python 2.6, 3.0, 3.1, 3.2, 3.3, 3.4
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
In some python versions (2.6, 3.0, 3.1, 3.2, 3.3, 3.4) the agent plugin 'apache_status'
crashed with the error message: "Exception (...: urlopen() got an unexpected keyword argument 'context'".
This happens only if an HTTPS connection is established.
The reason for this is that in previous Python versions "urllib.urlopen" did not support the 'context' parameter.
This werk introduces an alternative handling of "urllib.urlopen" for affected python versions.
If you want to use this feature you have to redeploy this agent plugin.
ID: 12143
Title: Graph dashlets: Optionally disable time range synchronization
Component: Multisite
Level: 1
Class: New feature
Version: 2.1.0i1
When a dashboard has multiple graph dashlets showing different time ranges, it
may be not intended to synchronize the time ranges by zooming into a single
graph. By default Checkmk synchronizes the time ranges and pins of all graphs
on a page.
This can now be disabled for each graph dashlet individually by setting the
graph rendering option "Do not follow timerange changes of other graphs on the
current page".
ID: 10614
Title: Improved hexagon visualization on dashboards
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
Host/Service statistics dashlet:
LI: Up hosts and OK services are now displayed in green again, not in grey as was recently implemented.
Site/Host overview dashlet:
LI: The dashlet is now responsive to dashboard filters.
LI: Host and service state colors are now in line with Checkmk standards. Before, down hosts were shown in yellow (now red) and unknown services as well as unreachable hosts in red (now orange).
LI: The positioning of hexagons in the dashlet was fixed so they do not overflow beyond the dashlet borders anymore.
ID: 12206
Title: downtime_script: changing script to use REST API endpoints
Component: Core & setup
Level: 1
Class: New feature
Version: 2.1.0i1
This werk rewrites the downtime script to make all calls use
endpoints of the REST API. The user can set and remove downtimes
for host, services, hostgroup and servicegroup.
ID: 12235
Title: Permissions issues for DB2 Linux agent plugin
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The Linux agent plugin for monitoring DB2 instances (<tt>mk_db2</tt>) had a
permissions issue when being deployed via the agent bakery. The plugin tried
to call itself as a DB2 instance user, however, the directory where the plugin
is located requires root permissions.
For this fix to come into effect, users have to re-bake and update the Linux
agent for all affected systems.