ID: 11007
Title: check_mk_agent.linux: option to exclude specific agent sections through agent bakery
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
This change allows the user to execute only selected sections of the Checkmk agent. For this
option, the user must configure the "Agent sections" WATO rule. The change will be applied with
the next deployed agent. An example of the configuration file can be found in agents/cfg_examples.
ID: 11075
Title: victorops: Fix invalid message_type (OK to RECOVERY)
Component: Notifications
Level: 1
Class: Bug fix
Version: 1.7.0i1
VictorOps seems to have tightened their webhook handling: OK is no longer
accepted as a message_type, according to their webhook docs it has to be
RECOVERY instead.
As a result, VictorOps incidents no longer were resolved by checkmk.
ID: 11040
Title: nfsiostat: don't crash if dots are present in mount point
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
For services that contained a '.' in the mount point the
check crashed. This is fixed.
ID: 10535
Title: Activate Changes: Now able to specifiy the number of parallel site activations
Component: WATO
Level: 1
Class: New feature
Version: 1.7.0i1
Earlier versions may have run into memory problems when too much sites were activated at the same time.
Each site was handled in a separate helper process. This consumed quite a lot of memory when your
WATO setup included lots (>50) of sites.
You can now configure how much helper processes are spawned during the activate changes phase.
If there are more sites to activate then available helper processes, the remaining sites are put into a
queue and will be processed once a helper process becomes idle again.
Per default the optimal number of helper processes is calculated automatically (up to 90% remaining RAM is used),
which should be OK for most setups. The new global settings option <tt>Maximum parallel processes during activate changes</tt> allows
you to adjust this value. The hardcoded minium value is 5.
ID: 11125
Title: f5_bigip_mem: Fix discovery of service
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The service sometimes got falsely discovered. It will now only be discovered if both OID and a value are present.
ID: 11073
Title: NagVis snapin: Fix empty content during refresh
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
When the NagVis snapin is used with a larger number of maps or objects on these
maps, the refresh of the map states takes some time. During longer refresh
times, the snapin was not displaying the maps at all.
The already known state is now shown during refresh until the new information
is available.
ID: 10907
Title: ucd_cpu_util: Fix CPU utilization calculation
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Fixed the calculation for the CPU utilization. The system value used the outdated values/OIDs.
No longer query the CpuRawKernel value, since its already included in the CpuRawSystem.
CpuRawSystem = CpuRawKernel + CpuRawWait
The system value gets computed as:
system = CpuRawSystem + CpuRawInterrupt + CpuRawSoftIRQ
(CpuRawInterrupt in this case is equal to IRQ)
ID: 11072
Title: Distributed environments: Improve config synchronization
Component: WATO
Level: 3
Class: New feature
Version: 1.7.0i1
Synchronizing configurations between the central and remote sites has taken too
much time in the past because the entire configuration was always synchronized.
Even files that are still present on the remote site were completely
synchronized, which led to increased computing effort, traffic and runtime.
This mechanism has now been replaced by an incremental mechanism. Before each
synchronization, the system determines which files already exist on the remote
site. Only those files are synchronized that differ from the central site.
For the migration from Checkmk 1.6 to 1.7 the change is compatible. Both
central 1.6 sites can communicate with remote 1.7 sites and 1.7 central sites
can communicate with 1.6 remote sites. Mixed environments should only be used
for migration purposes. In such a scenario, the previous synchronization
mechanism is used. After 1.7 this compatibility mode will be removed.
ID: 10988
Title: Periodic service discovery: Fix not working "rediscovery scheduled" on clusters
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Please note that if you have configured rules {{Periodic service discovery}}
for clusters then the service discovery is executed on the cluster nodes.
This may overlap with rules of the nodes.