[checkmk-commits] [tribe29/checkmk] 9df1d4: Improve background job / automation debugging

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 9df1d43de5571ab0d95de2cd50288e5a30cfab5e https://github.com/tribe29/checkmk/commit/9df1d43de5571ab0d95de2cd50288e5a3… Author: Lars Michelsen <lm(a)tribe29.com> Date: 2020-10-16 (Fri, 16 Oct 2020) Changed paths: M cmk/base/automations/check_mk.py M cmk/base/modes/check_mk.py M cmk/gui/watolib/automations.py Log Message: ----------- Improve background job / automation debugging The GUI log level now affects the verbosity of the output produced by automation commands. To get more diagnostic information on e.g. the service discovery page, you you can now increase the log level for automations in the GUI logging configuration which will a) give you more output of the GUI mechanic and b) of the actual communication with the target device. Previously the automations always used either "normal" output or "verbose" output in case of the service discovery automation. Change-Id: I198e017581962a8ab980f34fc5b015b49d95a9ff Commit: ef634c8cbbee22f666726a86bdb98f979578bf9d https://github.com/tribe29/checkmk/commit/ef634c8cbbee22f666726a86bdb98f979… Author: Lars Michelsen <lm(a)tribe29.com> Date: 2020-10-16 (Fri, 16 Oct 2020) Changed paths: M cmk/fetchers/_base.py M cmk/fetchers/snmp.py Log Message: ----------- Add some more debug logging to SNMP fetcher Change-Id: Iba5cb6dd0015705fb450afebcac057edf6461d88 Commit: 13c34c5a8895d3b51f5bdcb5ccd53e89198c5d36 https://github.com/tribe29/checkmk/commit/13c34c5a8895d3b51f5bdcb5ccd53e891… Author: Sergey Kipnis <sergey.kipnis(a)tribe29.com> Date: 2020-10-16 (Fri, 16 Oct 2020) Changed paths: M cmk/base/checkers/_abstract.py M cmk/base/checking.py R cmk/base/cpu_tracking.py M cmk/fetchers/controller.py A cmk/utils/cpu_tracking.py R tests/unit/cmk/base/test_cpu_tracking.py A tests/unit/cmk/utils/test_cpu_tracking.py Log Message: ----------- [CMK-5399] - add CPU tracking to fetcher - track cpu usage for all fetchers - deliver results of tracking as a log message(to be fixed in next CL) to Microcore - add context manager API to cpu_tracking module - unit test - move cpu_tracking to cmk.utils to avoid layer violation warning - introduce cpu_tracking.reset This is first part of the ticket: gathering data. Some details of implementation Unfortunately current codebase requires that we have some kind of global data(decorator cpu_tracking.track) to track cpu usage. This approach makes impossible the transfer of the context of cpu tracking outside the module(like in cmk...profile). We have chosen to use 'reset' together with starting of the gathering cpu info. This API(pair reset/start) may be changed in the future to be more elegant. Change-Id: Ia0c3f3ac34372a2910f5b009efc54f8081c67dbe Compare: https://github.com/tribe29/checkmk/compare/a25290a19b2c...13c34c5a8895