ID: 8912
Title: Kubernetes checks for jobs
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The special agent now delivers information for k8s
jobs. The check provides information on active and
terminated jobs and the job containers are counted
in the HW/SW inventory.
ID: 10042
Title: Fix exception caused by autochecks with integers as items
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.7.0i1
The calculation of check parameters during activate changes or checking
could cause an exception like "TypeError: expected string or buffer" when
a discovery function of a check created services using integers as items
instead of strings.
ID: 10041
Title: Reduce apache memory usage + Change check parameters API
Component: WATO
Level: 2
Class: Bug fix
Version: 1.7.0i1
We recognized that the 1.6 check parameter (ruleset) plugin mechanism (which
was based on classes and using the python abc module) consumed a lot more
memory than the previous plugin API.
The apache processes were ~50% bigger than in previous Checkmk releases which a
too large growth. The problem is that the apache processes are part of a
dynamic process pool which can scale from 5 to 64 processes (in the default
config). When your apache processes use 130 MB of memory, this means that you
would need to have ~8 GB of memory available to be able to handle high usage
peaks. In such a situation a single process growth of 50% is relevant and
should be avoided if possible.
If you have already ported your WATO check parameter plugins to 1.6 you will
now have to port it to the new mechanism.
The new plugin API for registering check parameters is similar to the 1.5 API,
but more explicit to make it easier to understand. For example the 'logins'
check parameter declaration looks like this:
C:+
from cmk.gui.i18n import _
from cmk.gui.valuespec import (
Integer,
Tuple,
)
from cmk.gui.plugins.wato import (
CheckParameterRulespecWithoutItem,
rulespec_registry,
RulespecGroupCheckParametersOperatingSystem,
)
def _parameter_valuespec_logins():
return Tuple(
help=_("This rule defines upper limits for the number of logins on a system."),
elements=[
Integer(title=_("Warning at"), unit=_("users"), default_value=20),
Integer(title=_("Critical at"), unit=_("users"), default_value=30)
],
)
rulespec_registry.register(
CheckParameterRulespecWithoutItem(
check_group_name="logins",
group=RulespecGroupCheckParametersOperatingSystem,
parameter_valuespec=_parameter_valuespec_logins,
title=lambda: _("Number of Logins on System"),
))
C-:
ID: 10058
Title: Windows Agent: Increased speed of processing data coming from plugins
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0b10
Previously, a plugin that generated large amounts of data could be interrupted
by the timeout. An example of such plugin is mssql.vbs.
Now this problem is solved and the Windows Agent agent fully supports such
plugins.
ID: 10057
Title: msoffice check works now correctly
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0b10
Previously bakery generated msoffice check config file with wrong name.
Additionally, bake agent may fail with crash
Now both errors had been fixed and nsoffice check works as intended
ID: 8909
Title: Exclude MSSQL instances from monitoring
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The MSSQL plugin may now be configured to exclude specific
instances from the monitoring. This is achieved with an extra
section in the configuration file. The new section looks like:
[instance]
exclude = inst1,inst2,inst3
ID: 8793
Title: notifications crash if non ASCII characters are present in the plugin output
Component: Notifications
Level: 1
Class: Bug fix
Version: 1.7.0i1
For bulk notifications this results in recurring notifications since
the corresponding spoolfile was not cleaned up. Non bulk notifications
were not sent multiple times. For both normal and bulk notifications
no "Final notification result" was produced in the "Host- and Service
notifications" view.
ID: 8909
Title: Exclude MSSQL instances from monitoring
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The MSSQL plugin may now be configured to exclude specific
instances from the monitoring. This is achieved with an extra
section in the configuration file. The new section looks like:
[instance]
exclude = inst1,inst2,inst3