ID: 7958
Title: ps: Allow to filter discovery by cgroup (Linux only)
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The checkmk agent for Linux hosts now also sends the <i>cgroup</i>
information proveded by the ps command. This allows users to filter
processes by their control group during discovery.
For instance you can use this to exclude processes running in Docker
containers.
See the help of the discovery rule "Discover Processes" for details.
ID: 7717
Title: Windows Agent 1.6 Beta 4: new features
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.6.0b4
Summary of the features introduced in Windows Agent beta 4:
- Asynchronous plugins with 'cache_age' set to 0 are supported now.
In previous version such plugins have been assumed as synchronous.
- The Uninstallation of the Windows Agent doesn't remove 'config' and 'state' directories from the Agent Data directory to prevent user data loss.
- The start of the Windows Agent may be delayed by a few seconds to allow asynchronous plugins to finish their work.
This feature has no effect for normal situation when agent is running as a service, but may be useful to test asyncronous plugins.
- Now the Agent uses next directories:
The Windows Agent installs own binary files in the directory "Program Files (x86)\checkmk\service"
For user and bakery data the Windows Agent uses the directory "ProgramData\checkmk\agent"
- The macroses used in the configuration files had been renamed
$BUILTIN_AGENT_PATH$ -> is C:/Program Files(x86)/checkmk/service/
$BUILTIN_PLUGINS_PATH$ -> is C:/Program Files(x86)/checkmk/service/plugins
$CUSTOM_AGENT_PATH$ -> is C:/ProgramData/checkmk/agent/
$CUSTOM_PLUGINS_PATH$ -> is C:/ProgramData/checkmk/agent/plugins
$CUSTOM_LOCAL_PATH$ -> is C:/ProgramData/checkmk/agent/local
- The logfile check_mk.log have been moved to the "ProgramData/checkmk/agent/log" directory
- The configuration files check_mk.user.yml and check_mk.yml had been revised, cleaned of old and unused data and better documented.
- The default timeout for all plugins is set to 60 seconds, previously the timeout was set to 30.
- Now all names in any yml configuration file with the leading underscore are considered invalid and skipped
from the output when the command showconfig is used.
ID: 7716
Title: Windows Agent 1.6 Beta 4: fixes
Component: Checks & agents
Level: 2
Class: Bug fix
Version: 1.6.0b4
Summary of the fixes introduced in beta 4 for Windows Agent
- the readme file extension had been changed from .md to .txt to be more Windows-friendly
- the logwatch configuration is correctly merged, including data from the config file check_mk.user.yml
in previous version, the agent only got entries from the check_mk.user.yml
now used all configurations file are used in the correct order: check_mk.yml, check_mk.bakery.yml and check_mk.user.yml
- the msexch section no longer sends invalid formatted section data, which caused the check to crash
- The processing of plugin had been reorganised. The execution order is now strictly defined according to simple rules:
"Top-down priority of patterns" and "Duplicate executables will be skipped".
More examples can be found in the current check_mk.user.yml.
- The Agent Update plugin is now correctly started and its output is correctly processed.
Previously Agent doesn't send output from the Agent Updater to the server.
- An empty local section is no longer sent
- Fixed error 104 during connection monitoring site to the 64-bit windows client.
Previously 64-bit version of the Agent may reset connection with error 104 if any async plugin didn't stop in time.
- Fixed an error with missing 'temp' folder for Agent Updater.
Due to strange glitch in Windows Agent folder 'temp' had been renamed to 'tmp'.
Previously the Agent Updater tried to find "temp" folder and if it was not available,
the Agent Updater wrote an error message and used the global fallback folder specified in the environment variable %temp%.
The Agent Updater now uses the 'tmp' folder within ProgramData\checkmk\agent
- The 1.5 Agent Updater no longer tries to do a second installation after the windows service was updated to version 1.6
This was caused by not-updated hash values in the old windows agent directory
The 1.6 Agent is now able to patch these values in the old agent directory, hereby preventing the agent updater to trigger another update.
ID: 8784
Title: bulk notifications were sent multiple times
Component: Notifications
Level: 2
Class: Bug fix
Version: 1.7.0i1
Werk #8783 introduced a bug where bulk notifications
were not cleaned up and sent multiple times. All
notification scripts that produce no plugin output
like e.g. asciimail are affected.
ID: 7992
Title: Add DATE_YEAR, DATE_MONTH, DATE_DAY report scheduler macros
Component: Reporting & Availability
Level: 1
Class: New feature
Version: 1.7.0i1
These macros can now be used e.g. in the names of the generated PDF report files
when storing them locally on the Checkmk server.