ID: 10040
Title: Fix wrong core host name in events when using host name rewriting
Component: Event Console
Level: 2
Class: Bug fix
Version: 1.7.0i1
The Event Console queries the monitoring core to find a match between the host
in the core and the origin of the event. In case you used the event rewrite
mechanism to change the host name, the lookup in the core was done with the
original host name of the event instead of the rewritten host name.
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: 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: 10040
Title: Fix wrong core host name in events when using host name rewriting
Component: Event Console
Level: 2
Class: Bug fix
Version: 1.7.0i1
The Event Console queries the monitoring core to find a match between the host
in the core and the origin of the event. In case you used the event rewrite
mechanism to change the host name, the lookup in the core was done with the
original host name of the event instead of the rewritten host name.
ID: 7944
Title: Fixed handling of unfresh services
Component: cmc
Level: 2
Class: Bug fix
Version: 1.7.0i1
The 1.6.0 branch introduced a regression: When a service was detected as
unfresh, the CMC terminated with a log message of the form:
host name mismatch in active check result: expected 'FOO', got 'BAR'
Even worse, this state was permanent: After restarting the same thing
happened again, so the only way to get out of this was to remove the CMC's
state file. Note that this only affected unfresh services, not hosts.
The problem was caused by an internal confusion of host name and service
name of the unfresh service, which has been fixed.
ID: 8858
Title: Fix broken distributed setup when Livestatus TLS is not enabled (1.6.0b5 regression, #7987)
Component: Site Management
Level: 2
Class: Bug fix
Version: 1.7.0i1
Werk #7987 broke distributed setups via Livestatus when Livestatus TLS is not enabled.
ID: 7755
Title: Jenkins: New special agent to query jenkins instances
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.6.0b4
Special agent to monitor job and build states of a jenkins instance. Beside
the state of the job it gives informations about the job score and the time
since the last successful build. It also outputs informations about the last
build, like the time the build was triggered, the build id, duration and
result.
For performance reasons, the number of recognized jobs is limited to three
nested folder levels.
ID: 7942
Title: Fixed dashlet refresh.
Component: Multisite
Level: 2
Class: Bug fix
Version: 1.7.0i1
Various dashlets didn't refresh automatically after they have been
rendered initially, e.g. the globes for host/service statistics.
This was a regression in the 1.6.0 branch and has been fixed now.
ID: 7943
Title: Fixed graph zooming via mouse wheel.
Component: Multisite
Level: 2
Class: Bug fix
Version: 1.7.0i1
The 1.6.0 branch contained a regression which broke the synchronized zooming
of graphs, you could even see JavaScript exceptions in the browser console
while zooming. This has been fixed.
ID: 8880
Title: Fix SNMP management board credentials
Component: Core & setup
Level: 2
Class: Bug fix
Version: 1.7.0i1
Monitoring of SNMP management boards did not work in the previous
1.6.0 releases when the management board credentials were different
from the host SNMP credentials.