ID: 10385
Title: Do not expose download credentials to the image history
Component: Other Components
Level: 1
Class: Bug fix
Version: 1.7.0i1
The previous "docker build" mechanism was using docker build arguments for
handing over the Checkmk enterprise download credentials to the docker image
build procedure. This was making the credentials available in the meta
information of the docker image, which may not be acceptable in many
situations.
If you simply want to use the Checkmk docker container, you don't need to care
about the details below. This is just relevant for the ones building own docker
images with Checkmk using the standard build logic.
This change switches the image build logic to use a small busybox based
container during image building that manages the secret download credentials
and provides it to the "docker build" command. These containers will either be
stopped and removed after the build finished successfully or after 180 seconds.
If you build images on your own, you don't have to change anything if you use
our build logic (docker/Makefile).
ID: 10199
Title: Bakery plugins must save the configuration into yml_store parameter
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
Previously the Bakery configured Windows Agent using <tt>check_mk.ini</tt>
configuration file: every script in <tt>enterprise/agents/bakery</tt> directory
could write own configuration data into the own file. All those files had
been later gathered into one <tt>check_mk.ini</tt> configuration file.
Since this release the Bakery configures Windows Agent using only
<tt>check_mk.bakery.yml</tt>. All data located in the ini file will be ignored.
To correctly configure Windows Agent you must use new parameter in your
<tt>bake_***</tt> function named <tt>yml_store</tt>. This parameter has type
YamlStore and imported automatically from <tt>agent_bakery_plugins.py</tt>.
Now the configuration data of all plugins are stored in a standard Python
dictionary, which replicates the structure of the Windows Agent's
configuration file.
The following sample bake function sets the agent port setting for the Yaml
file. It receives the configured port for the agent configuration and creates
two entries, "enabled" and "port" in the "global" section.
C+:
def bake_agent_port(opsys, conf, conf_dir, plugins_dir, yml_store):
# ^^^^^^^^^
global_section = yml_store.make_section["global"] # mandatory to get dict
# ^^^^^^
global_section["enabled"] = True # mandatory also
global_section["port"] = conf # configures the Agent port
# ^^^^ ^^^^
C-:
The function above creates the following definitions in the
<tt>check_mk.bakery.yml</tt>:
C+:
global:
enabled: True
port: 6551
C-:
ID: 10441
Title: emc_ecs_diskio: new disk IO check for Dell EMC ECS storage systems
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
New SNMP check for monitoring the disk IO for Dell EMC ECS (cloud storage system). Make sure to create the rule 'Hosts without system description OID' for this host.
ID: 10335
Title: mongodb: extension of replica set checks
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
Additional checks and information to monitor mongodb replica sets:
- replication lag between the primary and its members
- oplog statistics
- change of primary mode
- missing primary node
- total size of all indexes
For using this new feature, you have to re-deploy the agent with the new mongodb plugin.
ID: 10198
Title: Windows Agent can be configured to use also non-WMI API to get data about running processes
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously the Bakery could not set "use_wmi" option to "no" (false) in the Windows
Agent's configuration file. This error force the Agent to use only WMI API to
get information about running processes.
Now the error has been fixed and the Bakery generates the configuration
file for the Windows Agent correctly
ID: 10201
Title: Windows Agent configures Windows Firewall by default
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
Windows Agent configures Windows Firewall automatically upon installation
ID: 10495
Title: mssql_connections: Remove default levels 20, 50 which are not useful in general
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Due to very different MSSQL environments we cannot state default levels in
general. One result is that there are a lot of {{MSSQL Connections}} services
which report WARN but which may be OK.
If you count on these default levels for some {{MSSQL Connections}} services
you have to create rules {{MSSQL Connections}} for these services.