ID: 10787
Title: Fix missing new line in ESX agent which may break various sections and services may go UNKNOWN
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
ID: 10581
Title: fortigate_memory_base: Wrong interpretation of levels other than 'percent used'
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Using the WATO rule "Main memory usage (UNIX / Other Devices)", users could specify levels
as absolute values or percent and on used or free memory.
Previously only the 'percent used' combination worked correctly.
ID: 10579
Title: logwatch: Invalid check parameter: Undefined key 'pre_comp_group_patterns'
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
When configuring logwatch groups the above error could be displayed in
the WATO service configuration (however, the service functionality was not affected).
ID: 10677
Title: Windows plugins and local checks can be called using non-system account
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
Previously the plugins and local check were always called using <i>Windows
System account</i>. Such approach could restrict access to some resources,
for example, network shares. Now this problem has been resolved.
The new ruleset in Bakery <tt>Run plugins and local checks using non-system
account</tt> gives the possibility to run any Windows script using a given
user account.
There are two modes of the rule:
<i>group mode</i>, in this case Windows Agent provides its own internal
user in the requested group to run a script.
<i>user mode</i>, in this case the credentials for the given user account
must be fully specified.
The <i>group mode</i> is more secure, because no credentials need to be
stored anywhere, except in the agent internally. When using the
<i>user mode</i>, the provided credentials are stored on all Checkmk
servers to which the configuration is applied. Also, the credentials will
be baked into the distributed to target systems agent bakery
packages(MSI files).
The same functionality in Raw Edition can be achieved using Agent configuration
file.
To set <i>group mode</i> for desired plugin pattern you should assign
the name of the local group to the key <tt>group</tt>. To set <i>user mode</i>
for desired plugin pattern you should assign string with user name and password
separated with one space to the key <tt>user</tt>. Detailed example you may found
in the provided configuration file.
We highly recommend using the <i>group mode</i> whenever possible.
ID: 10679
Title: Windows Agent installs correctly cap file with empty files inside
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously the installation of the plugins.cap file with zero size files
was not possible.
Now the problem has been solved.
ID: 10758
Title: redis_info.persistence: New check to monitor Redis persistence
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
With this check you can monitor Redis instances. The check gets input from
the redis-cli command "info" and the resulting "Persistence" section. It
outputs the state of the last RDB (Redis Database Backup) save and AOF (Append
Only File) rewrite operation. Furthermore the time of the last successful RDB
save and the number of changes since the last dump.
Needs the agent plugin "mk_redis" to be installed.
ID: 10675
Title: mk_jolokia: Fixed baking configuration if server is stated in bakery rule "JMX monitoring of Java JVMs using Jolokia"
Component: agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
If server is stated in the bakery rule {{JMX monitoring of Java JVMs using Jolokia}}
the related configuration was wrong and an AttributeError occured while
executing the agent plugin {{mk_jolokia}}. You have to bake the related rules
and deploy the plugin and configuration file again.
ID: 10678
Title: Windows Agent fileinfo generates output entries for glob patterns in all cases
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously, if Windows Agent couldn't find files matching to an entry with a
glob pattern of <tt>fileinfo</tt> section, then the Agent wrote nothing and
Check MK monitoring site may wrongly decide, that the service doesn't exist.
Now <tt>fileinfo</tt> generates such entries always. If no files match to
a glob pattern in config, then the Agent creates a line with keyword
<tt>missing</tt>.
ID: 10618
Title: New versioning of CMC configs
Component: Core & setup
Level: 1
Class: New feature
Version: 1.7.0i1
The config files to CMC are now versioned.
When the core detects an incompatible version, it
provides instructions to the user to generate a
new configuration instead of crashing with a
segmentation fault.
The new versioning scheme is consistent with the
versioning of the state files.
<b>Note:</b>
This patch <b>requires</b> that the configuration be
generated once more with <tt>cmk -U</tt>.