ID: 10290
Title: Temperature check GUI: fix rendering crash when rules are set
Component: WATO
Level: 2
Class: Bug fix
Version: 1.7.0i1
10290 FIX Temperature check: fix rendering crash and reporting mismatch
When a check sends a device-specific levels in a specific format
the temperature rendering function of the service display
could crash due to a type mismatch. This werk fixes this crash.
Upon fixing this crash another bug was discovered and fixed. In the case
of user specified levels being set and the service being in mode
"Use your own levels if present, otherwise the device's", the device
levels were not ignored and thus the wrong levels were checked. This
is now fixed as well.
No additional action is needed.
ID: 10197
Title: Windows Agent can configure Windows Firewall
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
Previously Windows Firewall can prevent a connection to the Windows Agent(this
is the behavior by default) thus forcing a system administrator to configure
potentially every host with Windows Agent installed.
Now Windows Agent can configure the Windows Firewall self.
There are two possibilities:
- For Windows Agent service you may edit Checkmk configuration file adding
at the end:
C+:
system:
firewall:
mode: configure
C-:
and restart the Agent service or trigger a configuration reload.
- For exe file, for example, <tt>\path\to\check_mk_agent.exe<\tt> using command line
<tt>\path\to\check_mk_agent.exe fw -configure<\tt>
will configure Firewall correctly for <tt>\path\to\check_mk_agent.exe<\tt>
It is possible to make the agent remove the firewall configuration by setting
the mode option to "clear" in the agent configuration file or by executing
the command <tt>\path\to\check_mk_agent.exe fw -clear<\tt>
ID: 10428
Title: Distributed Agent Updates
Component: agents
Level: 2
Class: New feature
Version: 1.7.0i1
It is now possible to deploy baked agents via remote sites within a distributed
monitoring configuration. Prerequisites for this feature are a monitoring setup
using distributed WATO and the possibility to establish a connection from remote
sites to the central site via HTTP/HTTPS.
This feature is realized as follows: Update requests to the remote sites
get forwarded to the central site – The entire configuration and the agent
baking process is done on the central site. Agent packages that got requested
once at a remote site will get cached (as long as they are valid) there to save
unnecessary traffic. Additionally, the requested data will be checked for consistency
on the remote site, again to save unnecessary traffic to the central site.
In contrast to a single-site-setup, the update server for a host doesn't come exclusively
from the agent updater ruleset, but gets transmitted to the host on it's registration and
update requests. A host will receive the Checkmk site that it is monitored on as it's
update server.
Putting this together, an input of a Checkmk-server is only needed once on registration.
If a connection to the automatic update server is failing, the previously saved server
(from agent updater ruleset or from manual registration) will be contacted as a
fallback.
This feature also introduces a faciliated agent updater ruleset configuration - especially
when it comes to HTTPS handling - and some additional global settings that have to
be configured to enable the distributed agent updates.
All new or adapted configuration values get migrated in a way that maintains the behavior
of an existing agent updater ruleset.
For details about configuration and how to enable (or disable) this new feature, please
have a look at the <a href="https://checkmk.com/cms_agent_deployment.html"> Automatic Agent Updates</a>
article at the official Checkmk guide.
ID: 10299
Title: zerto: special agent and check for zerto rpo monitoring
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
This change allows the configuration of the Zerto Special Agent
which in turn allows retrieval and monitoring of RPO data. The required
credentials can be specified using a WATO rule.
ID: 10296
Title: timesyncd: time synchronisation check using systemd timesyncd service
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
This check behaves simarly to the already existing ntp check. It uses
the output of {timedatectl timesync-status} as sent by the agent. It
lists the information of the synchronised time server including the
server address, stratum, offset and jitter. On a running instance the
time is synchronised either using ntp or timesyncd. The agent therefore
determines the correct service and the respective check to use.
ID: 10286
Title: Netapp API Environment Check: check temperatures, fans, voltages and currents
Component: Checks & agents
Level: 3
Class: New feature
Version: 1.7.0i1
This werk adds the detection and checking of all detected fans, temperature,
voltage and current probes. The services (except the fan probes) will monitor
the pre-determined high and low levels (for warning and critical) given by the
API for each device and {WARN} or {CRIT} if the measured level is too high.
To monitor these new services only a service discovery of the host is needed.
For the fans, discrete checks are created which will {CRIT} if the sensor-state
differs from "normal".
There is no additional configuration.
ID: 10157
Title: Now using /dev/null instead of closing stdin in all POSIX agents
Component: Checks & agents
Level: 2
Class: Bug fix
Version: 1.7.0i1
Some programs might not be working when stdin is closed. A more portable
approach seems to use /dev/null as stdin.
ID: 10120
Title: Fixed error handling in automation calls
Component: WATO
Level: 2
Class: Bug fix
Version: 1.7.0i1
Under various circumstances, diagnostic output from automation calls (like
warnings etc.) got mangled with the result of the automation call itself.
This could break various things, e.g. activation on changes on local and
remote sites. This has been fixed, the diagnostic output is redirected
to var/log/web.log now.
ID: 10119
Title: Fixed CMC config generation in the presence of non-ASCII characters.
Component: config
Level: 3
Class: Bug fix
Version: 1.7.0i1
Non-ASCII characters in various places (e.g. group names) caused a failure in
the CMC config generation. This was a regression in 1.6.0 and has been fixed
now.