Branch: refs/heads/master
Home:
https://github.com/tribe29/checkmk
Commit: 07725e4444f663d2393bdb7648bd34e342d6437b
https://github.com/tribe29/checkmk/commit/07725e4444f663d2393bdb7648bd34e34…
Author: Maximilian Wirtz <maximilian.wirtz(a)tribe29.com>
Date: 2021-07-26 (Mon, 26 Jul 2021)
Changed paths:
A .werks/13065
M cmk/base/check_legacy_includes/size_trend.py
M cmk/base/plugins/agent_based/utils/size_trend.py
M cmk/gui/plugins/wato/check_parameters/asm_diskgroup.py
M cmk/gui/plugins/wato/check_parameters/cisco_mem.py
M cmk/gui/plugins/wato/check_parameters/esx_vsphere_datastores.py
M cmk/gui/plugins/wato/check_parameters/ibm_svc_mdiskgrp.py
M cmk/gui/plugins/wato/check_parameters/netapp_luns.py
M cmk/gui/plugins/wato/check_parameters/netapp_volumes.py
M cmk/gui/plugins/wato/check_parameters/network_fs.py
M cmk/gui/plugins/wato/check_parameters/utils.py
M tests/unit/checks/generictests/datasets/netapp_api_volumes.py
M tests/unit/cmk/base/plugins/agent_based/test_sap_hana_data_volume.py
Log Message:
-----------
13065 Absolute Levels on Filesystem Growth: Change Internal Representation From MB to
Bytes
The absolute levels for filesystem growth trends used to be Integer
fields. This was changed to the Filesize field, to be more convenient
when inserting larger warning levels.
Custom plugins which use the `size_trend` functions might need some
minor adjustments since internally these levels are now handled as bytes
instead of MB. If no custom plugins are used, no actions are necessary.
Change-Id: Ia08b049e6ca6eb0be13717124dc6b6b12ffbc5e7