ID: 14065
Title: azure_mysql: Monitor Azure database for MySQL
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
It's now possible to monitor Azure database for MySQL in Checkmk.
Six new checks have been added:
<ul>
<li>Microsoft Azure MySQL Database: CPU Utilization</li>
<li>Microsoft Azure MySQL Database: Connections</li>
<li>Microsoft Azure MySQL Database: Memory Utilization</li>
<li>Microsoft Azure MySQL Database: Network</li>
<li>Microsoft Azure MySQL Database: Replication</li>
<li>Microsoft Azure MySQL Database: Storage</li>
</ul>
The new services will be automatically discovered if you have
an Azure database for MySQL in the resource group already monitored
in Checkmk.
ID: 13915
Title: Wait 30 s between failed attempts to connect to InfluxDB
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
After a failed attempt to connect to an InfluxDB server, the core now
waits at least 30 s before trying again. This leads to, for example,
an optimized DNS traffic.
This delay of 30 s is not configurable by the end user.
ID: 14549
Title: <tt>mongodb_collections</tt>, <tt>mongodb_replica_set</tt>: Fix date parsing error
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Depending on the <tt>pymongo</tt> version on the host system, the two check plugins mentioned above
crashed with
C+:
TypeError: unsupported operand type(s) for /: 'str' and 'float'
TypeError: unsupported operand type(s) for -: 'str' and 'str'
C-:
ID: 14657
Title: service_discovery: addition of tabula_rasa mode
Component: REST API
Level: 1
Class: New feature
Version: 2.2.0i1
This werk adds the tabula_rasa mode to the execute service discovery endpoint.
ID: 13991
Title: Palo Alto: Check mode and local and peer state
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
The check plugin palo_alto used to be purely informative, i.e. the status of the service was always ok. Ha mode, ha local state and ha peer state are now checked to produce regular monitoring states with user-configurable values.
ID: 13914
Title: Escape semicolon in log entries
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
The "host & service history" view could not render plugin outputs
with semicolons correctly. This is due to the fact that semicolons
are interpreted as field separators.
We now replace the ";" characters with their HTML encoding, that
is, "%3B".
Note that Nagios silently replaces semicolons with colons (":")
in that case.
ID: 14548
Title: <tt>mk_logwatch</tt>: Make agent plugin executable under Python 2
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Werk <a href="https://checkmk.com/werk/14451">14451</a> introduced a regression which made the
<tt>logwatch</tt> agent plugin crash under Python 2. The <i>"Check_MK"</i> service of affected hosts
reported "Missing monitoring data for plugins: logwatch". The error message thrown by the plugin
when executed directly on the host read
C+:
Traceback (most recent call last):
...
ValueError: invalid literal for int() with base 10: ...
C-:
ID: 14503
Title: ups_test: crash with KeyError (0)
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The check <tt>ups_test</tt> used to crash with the error message 'KeyError
(0)'. This has been fixed: any unknown test results are shown as 'unknown'.