[checkmk-commits] [tribe29/checkmk] e1b14f: 12484 FIX Fix customgraphs in reports

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: e1b14fb50218eaa0a5f9e0c380b9f2afdde4712f https://github.com/tribe29/checkmk/commit/e1b14fb50218eaa0a5f9e0c380b9f2afd… Author: Óscar Nájera <oscar.najera(a)tribe29.com> Date: 2021-04-08 (Thu, 08 Apr 2021) Changed paths: A .werks/12484 Log Message: ----------- 12484 FIX Fix customgraphs in reports Customgraph report elements cause an exception. This is now fixed Change-Id: Id2e476e802085b9bce227197beb910b35893af45 Commit: f806fdbc9911d336945ee39a3de449bbd35f5123 https://github.com/tribe29/checkmk/commit/f806fdbc9911d336945ee39a3de449bbd… Author: Óscar Nájera <oscar.najera(a)tribe29.com> Date: 2021-04-08 (Thu, 08 Apr 2021) Changed paths: A .werks/12483 M cmk/gui/plugins/metrics/unit.py Log Message: ----------- 12483 Event rates in graphs can be of very small magnitude Event rates were displayed with at most a presision of 2 decimals on the graphs, and was generally a good format. Yet, there are some cases when monitoring very sporadic events, graphs would show a scale containing only zeros. After this werk, event rates follow the same scientific notation used on other metrics like floating point numbers, counts and percent. This allows to appropiately display numbers regardless of their domain range. Change-Id: Iac3839115327186d4fdfa16947d4c912237aa404 Compare: https://github.com/tribe29/checkmk/compare/7a3dabade9d7...f806fdbc9911