ID: 10033
Title: Flap detection settings for services: Could not be defined per service
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.7.0i1
The ruleset "Flap detection settings for services" could not be used to define
service specific flap detection settings as it was intended. The rules could
only be configured per host.
ID: 8897
Title: Plug-in configuration is correctly processed by the agent
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0b8
Previously, Windows Agent processed the plugin configuration
using the approach: the first rule wins.
Thus, each plugin can only use one rule for its configuration.
>From now on, the Windows Agent agent applies all the rules to each plugin,
provided that the rule file name pattern matches with the plugin name.
ID: 10031
Title: Warn about editing rules which conditions are not valid anymore
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
When a rule is opened for editing and an the rule edit dialog detected
an invalid previous value, it prints a warning message about this to
the user.
The same is now done for the rule conditions. In case e.g. a rule refers
to a tag group or tag that does not exist (anymore) in the current WATO
configuration, the dialog shows a warning message instead of silently
dropping the invalid option as it was done before.
ID: 10055
Title: The Windows Agent service loads correct configuration
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0b9
Previously, after installation from MSI, the Windows Agent service loaded
its own configuration too early, thus loading the default(fabric) configuration,
ignoring bakery configuration.
To use the configuration provided by bakery, you should restart the service
manually.
Since now Windows Agent loads the configuration only after updating the
Legacy Agent configuration and after installing the Bakery configuration.
ID: 8899
Title: Windows Agent only_from parameter works now correctly
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0b9
Previously in check_mk.user.yml, installed from the Windows Agent MSI,
the parameter 'only_from' was incorrectly initialized with an empty value.
This effectively prevented the setting of 'only_from' using Bakery,
because the user configuration is more prioritized than the bakery one.
Now the 'only_from' parameter is removed from check_mk.user.yml.
ID: 10030
Title: Still allow working with old customized builtin tag groups
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
With 1.4 some sample config tag groups have been changed to be "builtin"
tag groups. A prominent one is the "agent" tag group. Previous 1.6 releases
totally disallowed saving tag configs in case such a tag group was present.
To make the migration easier, the validation is now less strict for the 1.6.
It is possible to keep the old builtin tag group until updating to 1.7. With
1.7 these tag groups will not be usable anymore and have to be migrated.
ID: 8898
Title: New command line option 'restore' for Windows Agent
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0b9
This command line option restores original bakery configuration,
which consists from the next elements: check_mk.bakery.yml,
bakery plugins and checkmk.dat.
If installed Windows Agent has no bakery configuration, for example,
packaged agent, then nothing happens.
ID: 10038
Title: Fix cmk/check_mk_server:yes label related issues
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
This label was detected based on the asynchronously created agent section
'<<<omd_status>>>'. Because this section is not immediately available on the
first agent contact, this resulted in a label discovery after the second check
cycle.
Another issue was that the '<<<omd_status>>>' section was produced by non
Checkmk servers with older agent versions. This lead to a wrong label discovery.
We now use the dedicated '<<<labels>>>' section to create the label which is
produced once we find the command 'omd' on a system.
ID: 8909
Title: Exclude MSSQL instances from monitoring
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The MSSQL plugin may now be configured to exclude specific
instances from the monitoring. This is achieved with an extra
section in the configuration file. The new section looks like:
[instance]
exclude = inst1,inst2,inst3