ID: 7963
Title: brocade_fcport: Discover ports despite missing speed info
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
Previously, ports for which the device did not send an interface speed information
could not be discovered.
ID: 7449
Title: Fix Remove spurious perfdata in IF checks
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Remove repeated in & out perf data values
Remove perfdata for averaged average
ID: 8890
Title: Windows Agent 1.6: Configuration reloading had been restructured
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0b5
By default the Agent reloads the configuration files only on the start.
To manually reload all configuration files you can use command line:
check_mk_agent.exe reload_config
To automatically reload configuration files on every connect(the behavior
from beta 4 and earlier) you can set the environment variable CMA_AUTO_RELOAD
to yes
ID: 7960
Title: ps: Option to include process arguments in long-output
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
This Werk adds an option to include process arguments in the long-output
of the service.
If specified in the ruleset "State and count of processes", the list of
all the matching processes and their details in the long-output will
include up to the first N characters of each processes' arguments.
<b>Note:</b> This feature must be used with care, as the output may
include sensitive data like credentials.
ID: 8857
Title: Docker container: Add hook functions to docker entrypoint
Component: Linux Distributions
Level: 1
Class: New feature
Version: 1.7.0i1
With this change it is possible to to execute custom hook scripts during the
container startup. This is useful in case you want to integrate your own
logic into containers based on the Checkmk images.
These hooks have been created:
pre-create -
post-create
pre-start
post-start
To use them you need to
At these steps, all scripts within docker-entrypoint.d/hook-name are executed.
root@7ac2dc47037e:/# tree docker-entrypoint.d/
docker-entrypoint.d/
|-- post-create
| |-- 01_foo.sh
| |-- 02_bar.sh
| `-- 03_baz.sh
|-- post-start
| |-- 01_foo.sh
| |-- 02_bar.sh
| `-- 03_baz.sh
|-- pre-create
| |-- 01_foo.sh
| |-- 02_bar.sh
| `-- 03_baz.sh
`-- pre-start
|-- 01_foo.sh
|-- 02_bar.sh
`-- 03_baz.sh
ID: 8847
Title: Service discovery: Print warning instead of failing on discovery errors
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
The service discovery page of WATO was terminating the service discovery on the
first error, independent of which discovery function raised the error. In this
situation a single broken check could break the service discovery functionality
of WATO.
On the command line (cmk -I) the default behavious is to proceed with the other
discovery function when a single discovery function fails. This is now the
default behavior of the WATO discovery page.