Branch: refs/heads/master
Home:
https://github.com/tribe29/checkmk
Commit: cd0a3b3e98bac96068042b54d984c2135d53c7bb
https://github.com/tribe29/checkmk/commit/cd0a3b3e98bac96068042b54d984c2135…
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: 6bc4cfb71a2260b56abd793fb3bf3fe317629c1c
https://github.com/tribe29/checkmk/commit/6bc4cfb71a2260b56abd793fb3bf3fe31…
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/d662fd1547f2...6bc4cfb71a22