Branch: refs/heads/master
Home:
https://github.com/tribe29/checkmk
Commit: acf714dd7b1ee14240c5cd930c3d1c86b7301106
https://github.com/tribe29/checkmk/commit/acf714dd7b1ee14240c5cd930c3d1c86b…
Author: Christoph Rauch <christoph.rauch(a)tribe29.com>
Date: 2019-09-12 (Thu, 12 Sep 2019)
Changed paths:
M cmk/gui/plugins/metrics/check_mk.py
Log Message:
-----------
CMK-1767: S.M.A.R.T.: add missing metric translations
Change-Id: I327819377e9ffcdc1df76d94bad34c8673c9ddc4
Commit: a98f076210c4c609f0572f12c6cc582abfe933b1
https://github.com/tribe29/checkmk/commit/a98f076210c4c609f0572f12c6cc582ab…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2019-09-12 (Thu, 12 Sep 2019)
Changed paths:
A .werks/10038
M agents/check_mk_agent.linux
M checks/omd_status
Log Message:
-----------
10038 FIX Fix cmk/check_mk_server:yes label related issues
This label was detected based on the asynchronously created agent section
'<<<omd_status>>>'. Because this section is not immediately
available on the
first agent contact, this resulted in a label discovery after the second check
cycle.
Another issue was that the '<<<omd_status>>>' section was
produced by non
Checkmk servers with older agent versions. This lead to a wrong label discovery.
We now use the dedicated '<<<labels>>>' section to create the
label which is
produced once we find the command 'omd' on a system.
Change-Id: I81bf19060b4d7c8f98efd28472cf4855508a4ce9
Compare:
https://github.com/tribe29/checkmk/compare/bcdad89c95a8...a98f076210c4