Branch: refs/heads/master
Home:
https://github.com/tribe29/checkmk
Commit: a73945817bc836973a09c74d7b9d69e51ed523b3
https://github.com/tribe29/checkmk/commit/a73945817bc836973a09c74d7b9d69e51…
Author: Joerg Herbel <joerg.herbel(a)tribe29.com>
Date: 2021-06-02 (Wed, 02 Jun 2021)
Changed paths:
M cmk/utils/bi/bi_data_fetcher.py
M cmk/utils/bi/bi_lib.py
M cmk/utils/bi/bi_searcher.py
M cmk/utils/rulesets/ruleset_matcher.py
M tests/unit/cmk/utils/bi/bi_test_data/sample_config.py
M tests/unit/cmk/utils/bi/test_bi_search.py
M tests/unit/cmk/utils/rulesets/test_ruleset_matcher.py
Log Message:
-----------
Ruleset matching: Take host tag groups ids into account
Also the caching of hosts now uses both the group ids and the tag ids.
Previously, only the tag ids were used, which led to wrong machtes since
the tag ids are not required to be unique across different tag groups.
SUP-5957
Change-Id: I97f2918f0fca1ef8a484bdafca32e5705df43bd6
Commit: e6dec2e88a9ca2fc48ec10a7b7ea99bc22830f0c
https://github.com/tribe29/checkmk/commit/e6dec2e88a9ca2fc48ec10a7b7ea99bc2…
Author: Joerg Herbel <joerg.herbel(a)tribe29.com>
Date: 2021-06-02 (Wed, 02 Jun 2021)
Changed paths:
A .werks/12882
Log Message:
-----------
12882 FIX Host tags: Take tag groups into account when matching against rule conditions
Up to now, the matching of host tags against rule conditions was based solely on
on the tag ids. The ids of the tag groups were not taken into account. However,
tag ids are not required to be unique across different tag groups. Therefore,
if the same tag ids occur in multiple tag groups, ignoring the group ids can lead
to wrong results.
This werk fixes this issue. Tag group ids are now taken into account when checking
if a rule applies to a host, both for normal monitoring rules and BI aggregations.
SUP-5957
Change-Id: I13f174f924550ec31fbe6dc528973c652770a73f
Compare:
https://github.com/tribe29/checkmk/compare/3d8b27e66dac...e6dec2e88a9c