Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 92c7649a1b06f327a831a702af5a0865e17b6c9e
https://github.com/tribe29/checkmk/commit/92c7649a1b06f327a831a702af5a0865e…
Author: Joerg Herbel <joerg.herbel(a)tribe29.com>
Date: 2020-05-08 (Fri, 08 May 2020)
Changed paths:
A .werks/11092
M checkman/aws_cloudwatch_alarms_limits
M checkman/aws_dynamodb_limits
M checkman/aws_ebs_limits
M checkman/aws_ec2_limits
M checkman/aws_elb_limits
M checkman/aws_elbv2_limits
M checkman/aws_glacier_limits
M checkman/aws_rds_limits
M checkman/aws_s3_limits
M checkman/aws_wafv2_limits
M checks/aws.include
M checks/aws_cloudwatch_alarms_limits
M checks/aws_dynamodb_limits
M checks/aws_ebs_limits
M checks/aws_ec2_limits
M checks/aws_elb_limits
M checks/aws_elbv2_limits
M checks/aws_glacier_limits
M checks/aws_rds_limits
M checks/aws_s3_limits
M checks/aws_wafv2_limits
M cmk/gui/plugins/wato/check_parameters/aws.py
M locale/de/LC_MESSAGES/multisite.po
A tests-py3/unit/checks/generictests/datasets/aws_cloudwatch_alarms_limits.py
R tests-py3/unit/checks/generictests/datasets/aws_cloudwatch_alarms_limits_1.py
R tests-py3/unit/checks/generictests/datasets/aws_cloudwatch_alarms_limits_2.py
M tests-py3/unit/checks/generictests/datasets/aws_dynamodb_limits.py
A tests-py3/unit/checks/generictests/datasets/aws_ebs_limits.py
R tests-py3/unit/checks/generictests/datasets/aws_ebs_limits_1.py
R tests-py3/unit/checks/generictests/datasets/aws_ebs_limits_2.py
A tests-py3/unit/checks/generictests/datasets/aws_ec2_limits.py
R tests-py3/unit/checks/generictests/datasets/aws_ec2_limits_1.py
R tests-py3/unit/checks/generictests/datasets/aws_ec2_limits_2.py
M tests-py3/unit/checks/generictests/datasets/aws_ec2_limits_instances_rules.py
M tests-py3/unit/checks/generictests/datasets/aws_ec2_limits_vcpus.py
A tests-py3/unit/checks/generictests/datasets/aws_elb_limits.py
R tests-py3/unit/checks/generictests/datasets/aws_elb_limits_1.py
R tests-py3/unit/checks/generictests/datasets/aws_elb_limits_2.py
A tests-py3/unit/checks/generictests/datasets/aws_elbv2_limits.py
R tests-py3/unit/checks/generictests/datasets/aws_elbv2_limits_1.py
R tests-py3/unit/checks/generictests/datasets/aws_elbv2_limits_2.py
M tests-py3/unit/checks/generictests/datasets/aws_glacier_limits-1_regression.py
M tests-py3/unit/checks/generictests/datasets/aws_glacier_limits-2_regression.py
A tests-py3/unit/checks/generictests/datasets/aws_glacier_limits.py
R tests-py3/unit/checks/generictests/datasets/aws_glacier_limits_1.py
R tests-py3/unit/checks/generictests/datasets/aws_glacier_limits_2.py
A tests-py3/unit/checks/generictests/datasets/aws_rds_limits.py
R tests-py3/unit/checks/generictests/datasets/aws_rds_limits_1.py
R tests-py3/unit/checks/generictests/datasets/aws_rds_limits_2.py
A tests-py3/unit/checks/generictests/datasets/aws_s3_limits.py
R tests-py3/unit/checks/generictests/datasets/aws_s3_limits_1.py
R tests-py3/unit/checks/generictests/datasets/aws_s3_limits_2.py
M tests-py3/unit/checks/generictests/datasets/aws_wafv2_limits_1.py
M tests-py3/unit/checks/generictests/datasets/aws_wafv2_limits_2.py
Log Message:
-----------
11092 One service per region for AWS limits
With this werk, the monitoring of limits for AWS
services is split into one service per region. Before,
all regions were combined into a single service, which
resulted in potentially quite a lot of output and
caused problems with the graphs for 2 or more regions.
To apply this werk, users have to re-discover the
corresponding services, which will result in a loss
of the historically recorded metrics. This is best done
using "Automatic refresh (tabula rasa)" in the WATO-menus
of the affected hosts. Note that rules for upper or lower
levels created before this werk are not affected and will
apply to all newly discovered services. After installing
the werk, they can be modified to only apply to certain
regions.
Change-Id: I742f981bbd448291030c895c5fbad2ba601df32a
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: f47eb35377f3901885ddecbcba5a4d03dc543163
https://github.com/tribe29/checkmk/commit/f47eb35377f3901885ddecbcba5a4d03d…
Author: Sven Panne <sven.panne(a)tribe29.com>
Date: 2020-05-08 (Fri, 08 May 2020)
Changed paths:
M cmk/base/api/agent_based/section_types.py
M cmk/base/plugins/agent_based/hr_mem.py
M tests-py3/unit/cmk/base/api/agent_based/register/test_section_plugins_legacy_snmp_tree.py
Log Message:
-----------
Revert "SNMPTree: tighten typing"
This reverts commit 3865176840676bdb71eae4061a48cac48443af04, it breaks
pylint. The reason for this is a layering violation in cmk.update_config,
which pulls in cmk.base.config (and/or another of our 81 layering
violations... :-/ ).
Change-Id: I9bda38bfead02a36cf6b547234680fd8f8c7c260
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 490a933a6da865dd1f2ab67edcabfee2b0e67466
https://github.com/tribe29/checkmk/commit/490a933a6da865dd1f2ab67edcabfee2b…
Author: Tom Baerwinkel <tom.baerwinkel(a)tribe29.com>
Date: 2020-05-08 (Fri, 08 May 2020)
Changed paths:
R .werks/10535
M cmk/gui/background_job.py
M cmk/gui/plugins/config/base.py
M cmk/gui/plugins/wato/check_mk_configuration.py
M cmk/gui/plugins/wato/utils/__init__.py
M cmk/gui/watolib/activate_changes.py
M tests/unit/cmk/gui/test_background_job.py
M tests/unit/cmk/gui/watolib/test_watolib.py
M web/htdocs/js/modules/activation.js
Log Message:
-----------
Revert "WK10535: Activate Changes: Now able to specifiy the number of parallel site activations"
This reverts commit b967442a9b9ed2de3ce09b4c3cf97811fd744af8.
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 9eafc283c951d93dc5efba89e2736aaa3c40f562
https://github.com/tribe29/checkmk/commit/9eafc283c951d93dc5efba89e2736aaa3…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2020-05-08 (Fri, 08 May 2020)
Changed paths:
A .werks/11104
M checks/heartbeat_crm
M tests-py3/unit/checks/generictests/datasets/heartbeat_crm.py
Log Message:
-----------
11104 FIX heartbeat_crm: go to CRIT if data is too old
The service previously went to UNKNOWN instead of CRIT.
SUP-2837
Change-Id: I05f2445bbc4d314d9502f2863f640d801bac2464
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: b967442a9b9ed2de3ce09b4c3cf97811fd744af8
https://github.com/tribe29/checkmk/commit/b967442a9b9ed2de3ce09b4c3cf97811f…
Author: Andreas Boesl <andreas.boesl(a)tribe29.com>
Date: 2020-05-07 (Thu, 07 May 2020)
Changed paths:
A .werks/10535
M cmk/gui/background_job.py
M cmk/gui/plugins/config/base.py
M cmk/gui/plugins/wato/check_mk_configuration.py
M cmk/gui/plugins/wato/utils/__init__.py
M cmk/gui/watolib/activate_changes.py
M tests/unit/cmk/gui/test_background_job.py
M tests/unit/cmk/gui/watolib/test_watolib.py
M web/htdocs/js/modules/activation.js
Log Message:
-----------
WK10535: Activate Changes: Now able to specifiy the number of parallel site activations
Change-Id: Ib4153ed2a6be5c25eed5dd5f5a434cecb4bc261f
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 40c57ec6c70fc19a938a9f0985d0744349de5af1
https://github.com/tribe29/checkmk/commit/40c57ec6c70fc19a938a9f0985d074434…
Author: Sven Panne <sven.panne(a)tribe29.com>
Date: 2020-05-07 (Thu, 07 May 2020)
Changed paths:
M cmk/gui/watolib/rulespecs.py
Log Message:
-----------
Unobscurify register_rule a bit.
This commit just unrolls an obscure loop and moves code around a bit,
bringing related things closer together. Still obscure, though...
Change-Id: I52bed9f8e3f40ab5ac45f32e0bc012acf78a9456
Commit: 3180ac688f276640ea5229bd3bf18104bf43576c
https://github.com/tribe29/checkmk/commit/3180ac688f276640ea5229bd3bf18104b…
Author: Sven Panne <sven.panne(a)tribe29.com>
Date: 2020-05-07 (Thu, 07 May 2020)
Changed paths:
M cmk/gui/watolib/rulespecs.py
Log Message:
-----------
Make recent pylint happy with ManualCheckParameterRulespec.
The Rulespec class hierarchy is quite confusing to human readers and tools:
The constructors vary quite a lot, sometimes a parameter is a kwarg,
sometimes it's a simple arg, sometimes it's there, sometimes not. And to
make things even more interesting, the order of arguments varies, too.
OTOH, in register_rule() we pretend that we can handle those constructors in
a consistent way, which was simply not true previously. This commit fixes
that problem by adding match_type/name/factory_default kwargs with
compatible defaults to ManualCheckParameterRulespec.__init__.
When we use Python 3, we should probably make the epic argument lists
kwargs-only, which is the only sane way to use them (and we do this already
most of the time, anyway).
Change-Id: Ibb84248ab33afcb8adce9e545c17cceef0151a1a
Compare: https://github.com/tribe29/checkmk/compare/c30bb6320b87...3180ac688f27