ID: 2884
Title: mssql_blocked_sessions: the state of the blocked sessions is now configurable
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
ID: 2867
Title: check_http: client certificate and private key file parameters can now be set in wato
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
Users of these parameters should take extra care to verify the file names specified are valid.
ID: 1310
Title: blade_bx_powerfan: Check now uses better default leves
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i4
We got feedback that the default levels for this check are to high so we changed the levels to 20%/ 10% instead 50%/ 40%
ID: 1309
Title: multipath: Fixed name handling of multipaths
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i4
Old Versions of Check_MK added in some cases a whitespace at the end of the path name.
This has been fixed a while ago, but lead to the problem that the multipath check not longer
detected this paths. Now the check can handle again the old names. This means you can make an update
without to get an error, but you should do a rediscovery betimes to clean the thinks in the background (autochecks) up.
Please note that the Check_MK Discovery Service will detect the multipath devices again and it looks like they have the same name,
so do not wonder. It's cause of the autochecks.
ID: 2859
Title: Check_MK Discovery/Inventory and HW/SW Inventory services are now always using caches (if available)
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i4
The Check_MK services "Check_MK Discovery", "Check_MK Inventory" and "Check_MK HW/SW Inventory" need
data from the Check_MK agent on agent based hosts. These check were contacting the agent on their own
on every execution which could lead to logwatch messages not being processed by the agent because they
were already processed by the discovery/inventory checks.
We now set these checks to use the agent cache (if available and if recent enough). This makes the
checks only contact the agent when neccessary. This should never happen when the host is being monitored
regularly because the regular monitoring ensures that the cache is available and up-to-date.