ID: 15830
Title: Prevent Windows agent service crash in some cases
Component: Checks & agents
Level: 2
Class: Bug fix
Version: 2.2.0p5
In some cases Windows may report non-valid path for a running process.
This situation led to a crash of the Windows agent service.
With this release, Windows agent is ignoring non-valid path, thus
eliminating the problem.
ID: 15549
Title: Crash: mssql_blocked_sessions using pre-1.6 MSSQL agent plugin
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0p5
When using a pre-1.6 MSSQL agent plugin the {{mssql_blocked_sessions}}
check plugins would crash during discovery.
The pre-1.6 MSSQL agent plugins are now deprecated and can no longer be used.
Old still existing services will go to {{UNKNOWN}} and encourage you to update to a newer agent plugin version.
After a rediscovery the old services will vanish and new services will not be discovered.
Therefore an upgrade as described in <a href="https://checkmk.com/de/werk/6140">Werk #6140</a> is necessary.
ID: 15548
Title: Crash: Changing BGP Peer State Mapping ruleset from effective parameters
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0p5
When changing the BGP Peer State Mapping ruleset from the effective parameters view,
the view would crash not displaying the wanted ruleset.
Now this is fixed and the corresponding ruleset is being displayed
ID: 15547
Title: Add support for AKCP sensorProbe2+ sensors
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.3.0b1
AKCP sensorProbe2+ sensors can now be monitored via SNMP.
The following sensorProbe2+ sensors are now supported:
<ul>
<li>Humidity
<li>Temperature
<li>Dry Contact
<li>Smoke
<li>Water
</ul>
ID: 15767
Title: check_mk_agent: Fix crash in AIX and Solaris agents if agent profiling is on
Component: agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
AIX and Solaris agents would previously crash if agent profiling was activated
with LOG_SECTION_TIME=true.
The error in the agent output was:
C+:
./mk_filestats.py.log: cannot create [No such file or directory]
C-:
ID: 15882
Title: handling of 409 status code during activate changes
Component: Dynamic host configuration
Level: 1
Class: Bug fix
Version: 2.3.0b1
Prior to this werk, whenever the activate changes endpoint returned a 409 response
the DCD failed and logged the error without any helpful information on why this
error occurred. This werk improves the error and logging handling for this case.
ID: 15683
Title: notification_rules: implementation of rest-api endpoints
Component: REST API
Level: 1
Class: New feature
Version: 2.3.0b1
This werk introduces a new set of endpoints to the rest-api for the
configuration of notification rules.
Users can now via the rest-api do the following...
* Create a notification rule
* Update a notification rule
* Delete a notification rule
* Show a notification rule
* Show all notification rules
ID: 15634
Title: zypper: Enable Configuration of Monitoring States
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.3.0b1
The monitoring state of the plugin <tt>zypper</tt> depends on the presence of
package locks, security updates, recommended updates and other updates. With
this Werk, this behaviour is configurable via the rule <tt>Zypper Updates</tt>.
ID: 15953
Title: Support same graph multiple times in views
Component: metrics
Level: 1
Class: Bug fix
Version: 2.3.0b1
Before this werk, when adding the same graph multiple times to a view, only one of the graphs was
actually rendered. The other ones were displayed as empty frames.
ID: 15627
Title: <tt>winperf_if</tt>: Don't Show Connected as Operation Status
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
This change affects the <tt>Interface</tt> service on Windows nodes.
The plugin <tt>winperf_if</tt> would show the operation state 'Connected', even if no information
about the operation state was available. Note, the Windows Agent does not always provide the
operation state. This is the case when none of the plugins are enabled. The
check will now show 'Not available' instead.
If you see this state, we recommend that you enable the plugins to collect the necessary data. This
can be done via the <tt>Agent Bakery</tt> rule
<tt>Setup > Agents > Windows, Linux, Solaris, AIX > Agent rules > Network interfaces on Windows > Add rule: Network interfaces on Windows</tt>.
After potentially adjusting the agent, users should do re-discovery of the interface services. This
ensures that the discovered operation state is consistent with the current behaviour.
If it impossible to use the agent plugin, existing rules <tt>Network interface and switch port discovery</tt>
and <tt>Network interfaces and switch ports</tt> should to be adjusted instead.