ID: 10429
Title: Prevent tgz packages from modifying existing directories
Component: agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
This is a regression since Werk <a href=https://checkmk.com/check_mk-werks.php?werk_id=6711>#6711</a>.
When unpacking as root (as it is normally done), the .tar.gz agent packages from agent bakery
would modify access rights on existing directories like /etc and /usr/lib to have an access level of
0 (no access) on "others" (e.g. 755 changes to 750).
This bug is now fixed with this werk, as the agent bakery temporarily modifies it's umask when
baking the .tar.gz agent packages.
ID: 10423
Title: check_mk.agent_update: configuration of service state when agent deployment is globally disabled
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The current check_mk agent update service displays per default
a warning state when the agent deployment is globally disabled.
This feature now allows the user to select which state should be
displayed when this situation arises.
ID: 10471
Title: mk_logwatch: Add option to limit context
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
If the plugin mk_logwatch is configured to send context along with found messages,
the amount of data can become quite large. This werk adds the option of limiting
the context given for every warning or critical message to a given number of lines
befor and after the message. For instance, to limit the context to 3 lines before
and four lines after the message, set the option "limitcontext=3,4".
This option can be configured using the WATO rule "Text logfiles".
ID: 10440
Title: metrics: retrieve graph for 'Number of processes'
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The graph for 'Number of processes' was removed in some previous commit.
Some checks e.g. 'ps' where missing this graph.
It now got added again as a graph.
ID: 10494
Title: lnx_if: Fixed confusion of interface state UNKNOWN, DOWN if ethtool output is missing
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
If the command {{ethtool}} provides information about interfaces the
operational state of an interfaces is UP if ethtool outputs
{{Link detected: yes}} otherwise DOWN in case of {{Link detected: no}}.
If this output is missing then the interface flags in angle brackets of the
command {{ip}} are used to get the operational state. Out interpretation was as
following: If the flags contain UP, the operational status of the interface is
UP. If the flags contain DOWN, the status is DOWN otherwise it is UNKNOWN.
But we wrongly assumed that these flags contain DOWN. This has been fixed and
now it is handled as following: If the flags contain UP, the status is UP
otherwise it is DOWN.
ID: 10491
Title: Allow regular expressions in the ruleset "Processing of Piggybacked Host Data" for piggybacked host exceptions
Component: WATO
Level: 1
Class: New feature
Version: 1.7.0i1
Previously the maximum cache age, period and {{Check_MK}} service state could be
configured for single piggybacked hosts under {{Exceptions for piggybacked hosts}}.
There you had to state an exact piggybacked host name.
Now a list of piggybacked host names or regular expressions can be configured
in order to ease the configuration for a set of piggybacked host exceptions.
A regular expression must begin with {{~}}.