Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: c58fe73b8ea64415ca51f4e26bebee59ae7a3a99
https://github.com/tribe29/checkmk/commit/c58fe73b8ea64415ca51f4e26bebee59a…
Author: Timotheus Bachinger <timotheus.bachinger(a)tribe29.com>
Date: 2022-04-07 (Thu, 07 Apr 2022)
Changed paths:
A .werks/13419
M checks/cisco_cpu_multiitem
M tests/unit/checks/generictests/datasets/cisco_cpu_multiitem_regression.py
A tests/unit/cmk/base/plugins/agent_based/test_cisco_cpu_multiitem.py
Log Message:
-----------
13419 FIX cisco_cpu_multiitem: fix Werk #13413
Werk #13413 in version 2.0.0p22 caused that many valid
`cisco_cpu_multiitem` services vanished. This werk brings them back, but
in some cases with a different name: If your `cisco_cpu_multiitem` is
named `CPU utilization 0` those might vanish and be rediscovered as
`CPU utilization 1`.
Werk #13413 assumed that a 0 in cpmCPUTotalPhysicalIndex means that this CPU is
not supported at all. This assumption was wrong.
Co-authored-by: Benedikt Seidl <benedikt.seidl(a)tribe29.com>
Change-Id: I8e99accb6501eee0d00c4fcd3f922aad40293b70
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: e8862fbecd4ff7ccf974564b7c65e277d170c0f3
https://github.com/tribe29/checkmk/commit/e8862fbecd4ff7ccf974564b7c65e277d…
Author: Mazen Alkatlabee <mazen.alkatlabee(a)tribe29.com>
Date: 2022-04-07 (Thu, 07 Apr 2022)
Changed paths:
M tests/Makefile
M web/htdocs/js/index.ts
M web/htdocs/js/modules/async_progress.ts
M web/htdocs/js/modules/availability.ts
M web/htdocs/js/modules/backup.ts
M web/htdocs/js/modules/element_dragging.ts
M web/htdocs/js/modules/forms.ts
M web/htdocs/js/modules/help.ts
M web/htdocs/js/modules/hover.ts
M web/htdocs/js/modules/page_menu.ts
M web/htdocs/js/modules/prediction.ts
M web/htdocs/js/modules/reload_pause.ts
M web/htdocs/js/modules/service_discovery.ts
M web/htdocs/js/modules/sla.ts
M web/htdocs/js/modules/transfer.ts
M web/htdocs/js/modules/views.ts
M web/htdocs/js/modules/visibility_detection.ts
Log Message:
-----------
reformat typescript files with prettier
and include ts files in test-format-js
Change-Id: I820eadfd5c3197b47f6035a2af9b1558bc7c1c4f
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: ece4066615423f4ccffb485880a5ac2bae1f3f3b
https://github.com/tribe29/checkmk/commit/ece4066615423f4ccffb485880a5ac2ba…
Author: Sven Panne <sven.panne(a)tribe29.com>
Date: 2022-04-07 (Thu, 07 Apr 2022)
Changed paths:
M livestatus/src/MonitoringCore.h
M livestatus/src/NagiosCore.cc
M livestatus/src/NagiosCore.h
M livestatus/src/Query.cc
M livestatus/src/Query.h
M livestatus/src/Store.cc
M livestatus/src/test/TableQueryHelper.cc
Log Message:
-----------
Refactoring: Move User construction to MonitoringCore.
Change-Id: I2253f189e2171f73fa737e5e917ddec2634fcf91
Branch: refs/heads/2.1.0
Home: https://github.com/tribe29/checkmk
Commit: eb073c3f239fc4c6c8d38e15c97fe323c06d5aae
https://github.com/tribe29/checkmk/commit/eb073c3f239fc4c6c8d38e15c97fe323c…
Author: Sergey Kipnis <sergey.kipnis(a)tribe29.com>
Date: 2022-04-07 (Thu, 07 Apr 2022)
Changed paths:
A .werks/13853
Log Message:
-----------
13853 WATO supports windows agent controller parameters
Available parameters:
"Limit local access to the agent data to the agent controller" -
limits access to the monitoring data only to the windows agent controller.
"Legacy communication" - allows usage of the legacy communication
as a fallback in all cases.
"Agent internal TCP port used to communicate with controller" - allows
to change default TCP port used for communication between agent and
controller
For the Raw edition above mentioned parameters could be configured using
check_mk.user.yml. Corresponding keys are located in the system.controller
section
To set "Limit local access to the agent data to the agent controller"
use key "check".
To set "Legacy communication" use key "force_legacy".
To set "Agent internal TCP port used to communicate with controller" use
key "agent_channel"
Change-Id: I277c4afff896e13ba75c2a045858750f9cabc84f