16 Jan
2020
16 Jan
'20
1:51 a.m.
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 3e2cbfc6687932b702ee764c60c512e67cc6e589
https://github.com/tribe29/checkmk/commit/3e2cbfc6687932b702ee764c60c512e67…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2020-01-16 (Thu, 16 Jan 2020)
Changed paths:
M checks/cisco_cpu_memory
M checks/cisco_mem
M checks/cisco_mem.include
M checks/cisco_mem_asa
M checks/cisco_mem_asa64
M checks/mem.include
M tests/unit/checks/generictests/datasets/cisco_cpu_memory.py
M tests/unit/checks/generictests/datasets/cisco_mem.py
M tests/unit/checks/generictests/datasets/cisco_mem_asa64_5c2e2c9a3a465_regression.py
Log Message:
-----------
cisco_mem.include: adjust output to check_memory_element
CMK-3542
Change-Id: I4a8870ca29be1762425d374392115e7258e6837e
Commit: d259de1edcae7d7eb3070b890f887f8bdcba57d8
https://github.com/tribe29/checkmk/commit/d259de1edcae7d7eb3070b890f887f8bd…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2020-01-16 (Thu, 16 Jan 2020)
Changed paths:
A .werks/10582
M checks/fortigate_memory
A tests/unit/checks/generictests/datasets/fortigate_memory.py
Log Message:
-----------
10582 FIX fortigate_memory: Wrong interpretation levels other than 'percent
used'
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.
Change-Id: Ief9a16a4af69dc87543be8911483582d96da64e5
Commit: ed6738b2e3278b4d620577e4558e7c6d0abef1b7
https://github.com/tribe29/checkmk/commit/ed6738b2e3278b4d620577e4558e7c6d0…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2020-01-16 (Thu, 16 Jan 2020)
Changed paths:
M checks/fortigate_node
M checks/huawei_switch_mem
M checks/netscaler_mem
M checks/sophos_memory
M checks/tplink_mem
M tests/unit/checks/generictests/datasets/huawei_switch_mem.py
A tests/unit/checks/generictests/datasets/netscaler_mem.py
M tests/unit/checks/generictests/datasets/tplink_mem_1.py
M tests/unit/checks/generictests/datasets/tplink_mem_2.py
Log Message:
-----------
unify check output of some memory checks
CMK-3542
Change-Id: I99c6457b312a4faa33a02277af2141e264d75446
Commit: 520f8b94ce283e16bd988c364d0ee9059f30c2e3
https://github.com/tribe29/checkmk/commit/520f8b94ce283e16bd988c364d0ee9059…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2020-01-16 (Thu, 16 Jan 2020)
Changed paths:
A .werks/10580
M checks/aix_memory
M checks/brocade_sys
M checks/cisco_mem
M checks/cisco_mem_asa
M checks/cisco_mem_asa64
M checks/db2_mem
M checks/docker_container_mem
M checks/esx_vsphere_hostsystem
M checks/fortigate_memory
M checks/fortigate_memory_base
M checks/fortigate_node
M checks/hr_mem
M checks/huawei_switch_mem
M checks/innovaphone_mem
M checks/juniper_mem
M checks/juniper_screenos_mem
M checks/juniper_trpz_mem
M checks/mem
M checks/netscaler_mem
M checks/solaris_mem
M checks/sophos_memory
M checks/statgrab_mem
M checks/tplink_mem
M cmk/base/config.py
M cmk/gui/plugins/wato/check_mk_configuration.py
M cmk/gui/watolib/__init__.py
Log Message:
-----------
10580 Memory check plugins: Unify service descriptions
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
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
CMK-3542 SUP-24
Change-Id: I35272a69a9b97e85b2fea2e262dc7e7aaf29dd22
Commit: 74ecbbe51392b927c8b35957324c3592ab80f13a
https://github.com/tribe29/checkmk/commit/74ecbbe51392b927c8b35957324c3592a…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2020-01-16 (Thu, 16 Jan 2020)
Changed paths:
A .werks/10583
M checks/mem
M tests/unit/checks/generictests/datasets/mem_win_regression.py
Log Message:
-----------
10583 mem.win: Reformat output to match other memory services
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.
CMK-3542 SUP-24
Change-Id: I24871dcfc2dc6a5723022cffd059c0e94c0bb1a4
Commit: bdf559d0d9828a8e35bd1080a1e859f69146715c
https://github.com/tribe29/checkmk/commit/bdf559d0d9828a8e35bd1080a1e859f69…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2020-01-16 (Thu, 16 Jan 2020)
Changed paths:
A .werks/10584
M checks/docker_container_mem
M tests/unit/checks/generictests/datasets/docker_container_mem_agent_section.py
M tests/unit/checks/generictests/datasets/docker_container_mem_plugin_section.py
Log Message:
-----------
10584 FIX docker_container_mem: consider caches and drop zero metrics
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.
Change-Id: I9c3270ebd7ff2447d6363e18a48ef7c9a6de7d8e
Commit: 8c990897cadd6c5fa9bef9ac2d7a79ba73cd9c58
https://github.com/tribe29/checkmk/commit/8c990897cadd6c5fa9bef9ac2d7a79ba7…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2020-01-16 (Thu, 16 Jan 2020)
Changed paths:
M checks/aix_memory
M checks/mem.include
M tests/unit/checks/generictests/datasets/docker_container_mem_agent_section.py
M tests/unit/checks/generictests/datasets/emc_ecs_mem_1.py
M tests/unit/checks/generictests/datasets/solaris_mem.py
M tests/unit/checks/generictests/datasets/statgrab_mem_regression.py
M tests/unit/checks/test_mem_include.py
Log Message:
-----------
check_memory: include Swap even if it happens to be Zero
If the Swap info is present in the input data structure it will
be used in the output, even if it happens to be zero at the
time. It is only ommitted for callers that do not provide the
Key at all.
Change-Id: I54e9c3f599722f5c015160cceb90b8642562d5ee
Commit: 376ee947153fe6e9a69dd58da753fb4ca9bbf1a4
https://github.com/tribe29/checkmk/commit/376ee947153fe6e9a69dd58da753fb4ca…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2020-01-16 (Thu, 16 Jan 2020)
Changed paths:
A .werks/10585
M checks/aix_memory
M checks/docker_container_mem
M checks/emc_ecs_mem
M checks/mem
M checks/mem.include
M checks/solaris_mem
M checks/statgrab_mem
M cmk/gui/plugins/metrics/check_mk.py
M cmk/gui/plugins/wato/check_parameters/memory.py
A tests/unit/checks/generictests/datasets/aix_memory.py
A tests/unit/checks/generictests/datasets/aix_memory_swap.py
M tests/unit/checks/generictests/datasets/docker_container_mem_agent_section.py
M tests/unit/checks/generictests/datasets/docker_container_mem_plugin_section.py
M tests/unit/checks/generictests/datasets/emc_ecs_mem_1.py
M tests/unit/checks/generictests/datasets/emc_ecs_mem_2.py
M tests/unit/checks/generictests/datasets/emc_ecs_mem_3.py
M tests/unit/checks/generictests/datasets/solaris_mem.py
M tests/unit/checks/generictests/datasets/statgrab_mem_regression.py
M tests/unit/checks/test_mem_include.py
Log Message:
-----------
10585 mem.used, statgrab_mem, aix_memory, docker_container_mem, solaris_mem,
emc_ecs_mem: Unify service output
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
CMK-3542 SUP-24
Change-Id: I53ff7a21688b4545b653e05085360c41acc73ac0
Commit: 48fd2e1c5f87c7023343cc5aaff79bbf1f32c177
https://github.com/tribe29/checkmk/commit/48fd2e1c5f87c7023343cc5aaff79bbf1…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2020-01-16 (Thu, 16 Jan 2020)
Changed paths:
M .werks/10585
A .werks/10586
A .werks/10587
M checks/hr_mem
M tests/unit/checks/generictests/datasets/hr_mem.py
Log Message:
-----------
10585 hr_mem: Unify service output
10586 FIX hr_mem: Wrong handling of levels on free memory
10587 hr_mem: Now supports averaging
Change-Id: I4cf7af07ceeafefc2ee829505ac3b50601e0b016
Compare: https://github.com/tribe29/checkmk/compare/a80047ac3fad...48fd2e1c5f87