[checkmk-commits] [tribe29/checkmk] c19e2f: CMK-6472: Rework utils.interfaces

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: c19e2fd6b03b1d3ece96fa10258f2638f7aab885 https://github.com/tribe29/checkmk/commit/c19e2fd6b03b1d3ece96fa10258f2638f… Author: Andreas Umbreit <andreas.umbreit(a)tribe29.com> Date: 2020-12-17 (Thu, 17 Dec 2020) Changed paths: M cmk/base/plugins/agent_based/cadvisor_if.py M cmk/base/plugins/agent_based/utils/interfaces.py M cmk/gui/plugins/wato/check_parameters/interfaces.py M tests/unit/cmk/base/plugins/agent_based/test_aws_ec2.py M tests/unit/cmk/base/plugins/agent_based/test_aws_rds.py M tests/unit/cmk/base/plugins/agent_based/test_cadvisor_if.py M tests/unit/cmk/base/plugins/agent_based/test_lnx_if.py M tests/unit/cmk/base/plugins/agent_based/test_netapp_api_if.py M tests/unit/cmk/base/plugins/agent_based/test_winperf_if.py M tests/unit/cmk/base/plugins/agent_based/utils/test_interfaces.py M tests/unit/cmk/gui/plugins/wato/check_parameters/test_if_parameters.py Log Message: ----------- CMK-6472: Rework utils.interfaces - Remove obsolete in-check params transformation - Refactor "rates" list to a dataclass - Pass and use crit/warn levels as tuples instead of as single values - Stop throwing out perfvalues too early, sometimes alongside meaningless warn/crit levels - Rework bandwidth output: Output average metric only if needed for predictive levels, clearer code structure - Correctly apply levels for packet rates. This has been completely broken before. - Rework packets output: Yield simple metric and a notice-only result for all packet rates, don't output average metrics, clearer code structure - More convenient and unified format for errors, multicast and broadcast levels rulespecs Change-Id: Ibb5e4e8eb418d3a26630f2fb7f98b352b206b7c6