Branch: refs/heads/2.0.0
Home:
https://github.com/tribe29/checkmk
Commit: 98d4fdfb0b774e85e4dca6e6e5656f54a558e83f
https://github.com/tribe29/checkmk/commit/98d4fdfb0b774e85e4dca6e6e5656f54a…
Author: Ronny Bruska <ronny.bruska(a)tribe29.com>
Date: 2021-05-03 (Mon, 03 May 2021)
Changed paths:
A .werks/12858
M cmk/gui/plugins/views/painters.py
Log Message:
-----------
12858 FIX Clearer naming of host and service labels and tags in headings
SUP-6250
Change-Id: I3525c5f7be883b567a19b0789d01e0c591b69d71
Commit: 0058b647839a699858a01f9d1e70c69ed2be27b3
https://github.com/tribe29/checkmk/commit/0058b647839a699858a01f9d1e70c69ed…
Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com>
Date: 2021-05-03 (Mon, 03 May 2021)
Changed paths:
A .werks/12511
M cmk/gui/metrics.py
Log Message:
-----------
12511 FIX Any custom Perf-O-Meter destroyed all Perf-O-Meters
Users can implement their own Perf-O-Meters in
<i>local/share/check_mk/web/plugins/perfometer</i>.
Whenever a user did that in Checkmk 2.0.0 to 2.0.0p4,
<b>all</b> Perf-O-Meters vanished. Instead the error
message "Exception: _required_names" was displayed.
Internal note:
When loading the shipped 'metric' plugins in cmk.gui.metrics
that also includes the shipped perf-o-meters.
The *local* perf-o-meters are in a differently named
directory, and loaded from cmk.gui.views.py (which
cannot be changed easily).
In that case the the postprocessing is ommitted - so we
do the calculations on demand to avoid the
"KeyError: '_required_names'".
Change-Id: I9ff7544858fab978d5c3224d9dfe1d300e5fc9bb
Compare:
https://github.com/tribe29/checkmk/compare/6e46cec0643f...0058b647839a