ID: 11148
Title: agent_prometheus: correct handling of cAdvisor pod memory
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
In the previous version, the cAdvisor pod memory did not allow the handling
of multiple machine instances. This version now correctly processes the
information for both machine memory and memory limits.
ID: 11256
Title: Extension API change: html.header and html.top_heading require breadcrumb argument
Component: Multisite
Level: 1
Class: New feature
Version: 1.7.0i1
This change is only relevant in case you have custom GUI extensions that
implement custom HTML pages.
In case you do this, it is likely that you use the <tt>html.header</tt> or
<tt>html.top_heading</tt> methods. Once upgrading to 1.7 you will have to
update your code to hand over a breadcrumb as second argument.
This can be done like this:
C+:
from cmk.gui.plugins.main_menu.mega_menus import (
make_simple_page_breadcrumb,
MegaMenuSetup,
)
title = "My custom page"
html.header(title, make_simple_page_breadcrumb(MegaMenuSetup, title))
C-:
For more examples have a look at our code and search for the keyword
breadcrumb.
ID: 11142
Title: PostgreSQL: Differentiate idle from active connections
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
Previously, the agent plugin "mk_postgres" and the check plugin "postgres_connections" were not differentiating between "idle" and "active" connections.
With this werk, the data to differentiate those states is obtained and evaluated accordingly.
The WATO rule "Database Connections (PostgreSQL)" (renamed from "Database Connections (PostgreSQL/MongoDB)") has now a dedicated option for setting the levels for "active" and "idle" connections.
In case the rule was used previously, the default connection type for PostgreSQL will be "active" as the old agent was excluding "idle" connections.
<b>Note:</b> As this WATO rule was applicable as well for MongoDB, this change will be incompatible to previously existing MongoDB rules set with "Database Connections (PostgreSQL/MongoDB)". If this is applicable for your setup, perform the following steps:
<li> If you're monitoring both PostgreSQL <b>and</b> MongoDB: keep the old rule "Database Connections (PostgreSQL/MongoDB)" before updating to this werk.</li>
<li> If you're monitoring MongoDB <b>only</b>: delete the old rule "Database Connections (PostgreSQL/MongoDB)" before updating to this werk</li>
<li> Create a new rule with your previous settings for MongoDB with the new rule "Database Connections (MongoDB)" </li>
ID: 11223
Title: aix_diskiod: Switch to new diskstat-ruleset
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The check <tt>aix_diskiod<\tt> now uses the rules defined under the
ruleset "Levels for disk IO" instead of "Levels on disk IO (old style
checks)". User-defined rules have to be adjusted to account for this.
ID: 10127
Title: Do not remove acknowledgements for retries.
Component: cmc
Level: 1
Class: Bug fix
Version: 1.7.0i1
When a non-sticky acknowledgement has been set for a host/service in a soft
non-OK state, it has been removed when it stayed in a soft non-OK state in
the next check cycle (i.e. after a retry). This behavior was unexpected
for the user and inconsistent with the way Nagios behaves, so this has been
fixed.
ID: 10852
Title: mk_oracle.ps1: Fixed missing sqls in rman section
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
For Oracle databases with version lower than 12.1 there has been some missing
sqls in the plugin for Windows. This has been fixed with this werk. To
benefit from this change, you will need to replace the plugin on the Oracle
database host.
ID: 11305
Title: config: drop support of 'precompile_params'
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
This werk only affects users who have developed their own plugins using the 'precompile function' feature.
If you are not aware of this feature, you are most likely not affected.
The support of this feature is now dropped, so if you have used it, please adapt your code accordingly.
Otherwise your check function will not be passed the expected parameters.
Have a look at the commit history of the sap or fileinfo plugins for reference.
ID: 11233
Title: Manual checks: Do not overwrite static parameters with check group parameters
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Example:
If you have configured the manual check {{State and count of processes}} and
there's another rule {{State and count of processes}} from {{Parameters for
discovered services}} which also matches on the manual check then the manual
parameters are overwritten with the parameters for discovered services.
This may concern all manual checks and the related parameters for discovered
services.
ID: 11255
Title: Disable dangerous commands on hosts / services by default
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
In the views you have the option to execute commands on the visible
hosts or services. The most popular ones are the ones for setting
downtimes or acknowledging problems.
Significantly less used, but rather dangerous, commands include "Toggle
notifications", "Toggle active checks", "Toggle passive checks" and "clear
modified attributes".
These commands modify the behaviour of the core for the selected objects, e.g.
checks or notifications are deactivated, which overwrites the configuration of
the core. This can easily lead to confusion, as it is not very transparent for
which objects this modification is active.
The commands were previously only available by default for users with the role
"admin". We have now also withdrawn these rights from the role "admin" by
default.
Admins who still need these commands can reactivate the rights under "Roles &
Permissions" in the configuration.