ID: 10760
Title: Fix missing "Log: Output" column
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
If you edited existing views which used the column "Log Entries: Log Output",
the column field was empty and this option was not available to choose.
This has been fixed.
ID: 7279
Title: CME Snapshot generation: Improved performance by using more processes for the config computation
Component: WATO
Level: 1
Class: New feature
Version: 1.7.0i1
ID: 10634
Title: wmi.include: display the unit for levels in status detail of a service
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
In the status details of a service, when the warn/crit message is shown,
it is now possible to display the unit of the levels. E.g. for seconds 's' or millisecond 'ms'.
This change relates to checks using the wmi.include
ID: 10583
Title: mem.win: Reformat output to match other memory services
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The previous output "Memory usage 12.3% (12.30 GB/100.00 GB)" is now displayed as
"RAM: 12.3% - 12.30 GB of 100.00 GB". This is in line with several other memory check plugins.
ID: 10582
Title: fortigate_memory: Wrong interpretation levels other than 'percent used'
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Using the WATO rule "Main memory usage (UNIX / Other Devices)", users could specify levels
as absolute values or percent and on used or free memory.
Previously only the 'percent used' combination worked correctly. Now 'percent used' and
'percent free' are supported, while absolute values will result in a warning state,
as this device does not provide absolute values.
ID: 10580
Title: Memory check plugins: Unify service descriptions
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
Several Memory check plugins have been unified with respect to their service
description, which is now simply "Memory" or "Memory $ITEM$".
In order to use these new service descriptions you have to enable them below
{Global settings}, {Use new service descriptions}. Renaming of existing services
has many implications - including existing rules, performance data and availability
history - these renamings are disabled per default for existing installations.
Here you can switch to the new descriptions for selected check types.
Renaming the services will mean you loose all historic data. If you want to rename
the services but keep the recorded metrics, you have to rename the RRD files in
<tt>~/var/pnp4nagios/perfdata/$HOST$</tt> or <tt>~/var/check_mk/rrd/$HSOT$</tt>
according to the service name change.
Affected check plugins are:
LI:aix_memory
LI:brocade_sys.mem
LI:cisco_mem
LI:cisco_mem_asa
LI:cisco_mem_asa64
LI:db2_mem
LI:docker_container_mem
LI:esx_vsphere_hostsystem.mem_usage
LI:esx_vsphere_hostsystem.mem_usage_cluster
LI:fortigate_memory
LI:fortigate_memory_base
LI:fortigate_node.memory
LI:hr_mem
LI:huawei_switch_mem
LI:innovaphone_mem
LI:juniper_mem
LI:juniper_screenos_mem
LI:juniper_trpz_mem
LI:mem.used
LI:mem.win
LI:netscaler_mem
LI:solaris_mem
LI:sophos_memory
LI:statgrab_mem
LI:tplink_mem
ID: 10585
Title: mem.used, statgrab_mem, aix_memory, docker_container_mem, solaris_mem, emc_ecs_mem: Unify service output
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The output of these check plugins is now formatted in a clearer way, in line with other memory checks.
For instance: Output previously formatted as
54.70 GB used (46.70 GB RAM + 8.00 GB SWAP, this is 89.2% of 61.33 GB RAM + 8.00 GB SWAP)
will now read
Total (RAM + Swap): 89.19% - 54.70 GB of 61.33 GB RAM, RAM: 76.14% - 46.70 GB of 61.33 GB, Swap: 100% - 8.00 GB of 8.00 GB
ID: 10584
Title: docker_container_mem: consider caches and drop zero metrics
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously the caches where not taken into account correctly, this has been fixed.
Users might observe a slight drop in the used memory metric.
In addition, the swap metric is no longer produced, as it allways reported zero.
ID: 10586
Title: hr_mem: Wrong handling of levels on free memory
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Using the WATO rule "Main memory usage (UNIX / Other Devices)", users could specify levels
as absolute values or percent and on used or free memory.
Previously only the levels on 'used' worked correctly. Now levels on free memory are supported
as well.
ID: 10587
Title: hr_mem: Now supports averaging
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
Previously the averaging option of the WATO rule "Main memory usage (UNIX / Other Devices)"
was not supported by the check plugin.