[checkmk-commits] [tribe29/checkmk] 7d4d01: 7493 FIX veeam_tapejobs: fix mixed up running time...

Branch: refs/heads/1.6.0 Home: https://github.com/tribe29/checkmk Commit: 7d4d01617e3c7a4c83eac4afa11255aa5cfa00e1 https://github.com/tribe29/checkmk/commit/7d4d01617e3c7a4c83eac4afa11255aa5… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2019-07-04 (Thu, 04 Jul 2019) Changed paths: A .werks/7493 M checks/veeam_tapejobs A tests/unit/checks/generictests/datasets/veeam_tapejobs.py Log Message: ----------- 7493 FIX veeam_tapejobs: fix mixed up running time for running jobs Main change: use job_id to get the item state Along the way: * leverage the power of the check API * reorganize output to yield * add a test Change-Id: I870ce834580bedc776b1cdccf87c255617852871 Commit: aa8fd53c82f515c7354987b50cd400cd500b331a https://github.com/tribe29/checkmk/commit/aa8fd53c82f515c7354987b50cd400cd5… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2019-07-04 (Thu, 04 Jul 2019) Changed paths: A .werks/7945 M checks/veeam_tapejobs M tests/unit/checks/generictests/datasets/veeam_tapejobs.py Log Message: ----------- 7945 FIX veeam_tapejobs: treat idle background jobs like working ones Previously idle backgroud jobs went to a {CRIT} state right away. They are now treated in the same manner as working backgroud jobs, going to {WARN} or {CRIT} when the corresponding configured (or default) levels are exceeded. Change-Id: Ibd0539e6d25f96c96e1cd17b0806c914dd849aa6 Compare: https://github.com/tribe29/checkmk/compare/670f49a9f9f7...aa8fd53c82f5