ID: 10020
Title: winperf_tcp_conn: fix for parse function of winperf tcp check
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
This is a bug fix where the wrong information was previously retrieved during the parse procedure.
ID: 10006
Title: mk_logwatch: Do not crash upon non-matching optional subgroups and rewrites
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The agent plugin mk_logwatch crashed in case you had rewrite patterns defined and the
triggering regular expression contained non-matching optional subgroups.
ID: 10008
Title: mk_logwatch: acceppt '1'/'0' and 'yes'/'no' for boolean options
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
>From version 1.6.0b1 to 1.6.0b9 the boolean configuration obtions needed to be
set to 'true' or 'false', while earlier versions also allowed '1' or '0'.
mk_logwatch now understands (caseinsensitive) 'true', 'false', 'yes', 'no', '1',
and '0'.
ID: 10016
Title: mk_docker.py: crash in diskstat section
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The plugin in version 1.6.0b9 could not create the diskstat section.
ID: 10056
Title: Windows Agent command line option 'reload_config' starts/stops plugins
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0b9
Earlier 'reload_config' did not try to run asynchronous plugins.
Thus, the option was useless for the automatic update of the
agent with the Agent Updater plugin.
The Windows Agent now starts and stops asynchronous plugins according
to the configuration just loaded.
ID: 10014
Title: lnx_quota: Do not crash if no user quotas are present
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
lnx_quotas no longer crashes if no user quotas are present and no rules are defined.
ID: 10106
Title: GUI: Fix mismatched unit on PING packet-loss graph
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously the units were ms, which is wrong. Now it is displayed in percent.
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.