Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: 479bfc814033067c0439a0110cf8bd4ed30fb4e1
https://github.com/tribe29/checkmk/commit/479bfc814033067c0439a0110cf8bd4ed…
Author: Lukas Lengler <lukas.lengler(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
A .werks/11711
M agents/modules/windows/BUILD_NUM
M agents/plugins/mk_logwatch.py
M virtual-envs/windows/3.8/Pipfile
Log Message:
-----------
11711 FIX mk_logwatch for Windows
If the mk_logwatch agent plugin was used no Agent Output was created and
the HW-/SW Inventory would fail aswell. Therefore the agent plugin could
not be used for Windows.
The reasons for that were:
* In Python 3 sys.stdout returns \r\n as linebreak for Windows.
Checkmk can't handle this therefore we removed it by replacing
the default sys.stdout.
* The win32api module could not be imported because pywin32 was not installed.
Now pywin32 is installed by default.
Change-Id: I670eefb86b54f89b0464617f1e24fcfc00fdd396
Commit: 899c8d82033558110189914eee72286367e387c7
https://github.com/tribe29/checkmk/commit/899c8d82033558110189914eee7228636…
Author: Lukas Lengler <lukas.lengler(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
A .werks/11713
Log Message:
-----------
11713 FIX PySNMP: Opaque Handling
If your SNMP device used the type "Opaque" to send
floats the values were not formatted properly which
caused some crashes later.
The error occured if Checks tried to use these corrupted
values. Error patterns looked like this:
ValueError: could not convert string to float: '\x9fx\x04?B\x8f\\'
Now the Opaque value is formatted.
Change-Id: I60f888d6004231b87b7cc7472af3c0c4385f21c8
Compare: https://github.com/tribe29/checkmk/compare/a89a5ec6e32b...899c8d820335
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: f0abbb319763ee4b7a018e180430f1ee7a9a9760
https://github.com/tribe29/checkmk/commit/f0abbb319763ee4b7a018e180430f1ee7…
Author: Lukas Lengler <lukas.lengler(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
A .werks/11710
Log Message:
-----------
11710 FIX PySNMP: No longer return empty string
The SNMP Backend needs to return an empty string for walks if no result
is found for one OID in the walk because Checkmk can't handle this.
But PySNMP returned an empty string even if nothing was found for the
walk OID.
If no result is found for this OID the walk should be completely empty.
This was not the case for PySNMP which caused some issues with certain checks.
Now we return nothing if no result was found for the walk.
Change-Id: Ic2abcee7c5ed09ce349ee44441581126165a7469
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: a89a5ec6e32b63357a42e5d70e180384b8670373
https://github.com/tribe29/checkmk/commit/a89a5ec6e32b63357a42e5d70e180384b…
Author: Lukas Lengler <lukas.lengler(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
A .werks/11710
Log Message:
-----------
11710 FIX PySNMP: No longer return empty string
The SNMP Backend needs to return an empty string for walks if no result
is found for one OID in the walk because Checkmk can't handle this.
But PySNMP returned an empty string even if nothing was found for the
walk OID.
If no result is found for this OID the walk should be completely empty.
This was not the case for PySNMP which caused some issues with certain checks.
Now we return nothing if no result was found for the walk.
Change-Id: Ic2abcee7c5ed09ce349ee44441581126165a7469
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: c7554a473e6a5448cea1903a74f4f765723d24c5
https://github.com/tribe29/checkmk/commit/c7554a473e6a5448cea1903a74f4f7657…
Author: Sven Panne <sven.panne(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
M livestatus/src/LogCache.h
M livestatus/src/TableLog.cc
M livestatus/src/TableStateHistory.cc
Log Message:
-----------
Refactoring: Introduce LogCache::empty().
Fiddling around with iterators directly is extremely error-prone,
this change removes one use case.
Change-Id: I66ea39801a9ad4700fb194f96cb8426c028c5f6b
Commit: 9f27f9c9bee5cbb62828205b3ac5dac85b37c320
https://github.com/tribe29/checkmk/commit/9f27f9c9bee5cbb62828205b3ac5dac85…
Author: Lukas Lengler <lukas.lengler(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
A .werks/11711
M agents/plugins/mk_logwatch.py
Log Message:
-----------
11711 FIX mk_logwatch for Windows
If the mk_logwatch agent plugin was used no Agent Output was created and
the HW-/SW Inventory would fail aswell. Therefore the agent plugin could
not be used for Windows.
The reasons for that were:
* In Python 3 sys.stdout returns \r\n as linebreak for Windows.
Checkmk can't handle this therefore we removed it by replacing
the default sys.stdout.
* The win32api module could not be imported because pywin32 was not installed.
Now pywin32 is installed by default.
Changes related to this werk:
* Fix \r in agent output : 33ec94a8cf82a7b75e1350e1a5f83223c6a3bfe6
* Increase BUILD_NUM : 634f749eacd06df08c3548a50589c1e8c9f527ea
* pypiwin32 -> pywin32 : b19cc9fd2d5c605500b9bd017abea0edf4a461ce
* pypiwin32 to Pipfile : c50bbc7dc489331b9cbef35f7a7768f96c00bed4
Change-Id: I670eefb86b54f89b0464617f1e24fcfc00fdd396
Compare: https://github.com/tribe29/checkmk/compare/85c7406f5d72...9f27f9c9bee5
Branch: refs/heads/1.6.0
Home: https://github.com/tribe29/checkmk
Commit: f864098a613139e52f793ee6f21a9aae19302bdb
https://github.com/tribe29/checkmk/commit/f864098a613139e52f793ee6f21a9aae1…
Author: Sven Panne <sven.panne(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
M livestatus/src/LogCache.h
M livestatus/src/TableLog.cc
M livestatus/src/TableStateHistory.cc
Log Message:
-----------
Refactoring: Introduce LogCache::empty().
Fiddling around with iterators directly is extremely error-prone,
this change removes one use case.
Change-Id: I66ea39801a9ad4700fb194f96cb8426c028c5f6b
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: acd809924fbd6e834080f58a23bd8267626900fe
https://github.com/tribe29/checkmk/commit/acd809924fbd6e834080f58a23bd82676…
Author: Sven Panne <sven.panne(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
M livestatus/src/LogCache.h
M livestatus/src/TableLog.cc
M livestatus/src/TableStateHistory.cc
Log Message:
-----------
Refactoring: Introduce LogCache::empty().
Fiddling around with iterators directly is extremely error-prone,
this change removes one use case.
Change-Id: I66ea39801a9ad4700fb194f96cb8426c028c5f6b
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: 12b8dd8cb978affebb9a1a89b8cbb38eb9f19480
https://github.com/tribe29/checkmk/commit/12b8dd8cb978affebb9a1a89b8cbb38eb…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
A .werks/11752
M cmk/base/checkers/snmp.py
M cmk/base/config.py
M cmk/base/default_config/base.py
M cmk/gui/plugins/wato/check_mk_configuration.py
M cmk/gui/watolib/__init__.py
M tests/unit/cmk/gui/watolib/test_rulespecs.py
Log Message:
-----------
11752 FIX Management board: SNMP bulk walk can now be configured
SNMP Management boards were previously contacted with different SNMP settings.
SNMP management boards on non-SNMP hosts always used SNMPv1 (no bulk walk)
while SNMP management boards of hosts that are also monitored with SNMP,
inherited the bulk walk option from the host.
With Checkmk 2.0 it is now possible to explicitly configure this setting using
the ruleset "Management board SNMP using bulk walk (enforces SNMP v2c)".
Sites created with Checkmk 2.0 or newer will automatically use SNMPv2 and bulk
walks for all SNMP management boards. For compatibility reasons the behaviour
of existing sites is kept as initially described. However, in case your devices
support SNMPv2 and bulk walks, it is highly recommended to use it, for performance
reasons. In case you want to change to SNMPv2, you can create a rule without
condition in the ruleset "Management board SNMP using bulk walk (enforces SNMP
v2c)" to switch the default to SNMPv2 and bulk walks.
Change-Id: I9d80789a8ccefcbbdb4a0753f0c386e5238a517b
Commit: 0df136c7f3fd0fbcd68a9db09e7cda26a4f51044
https://github.com/tribe29/checkmk/commit/0df136c7f3fd0fbcd68a9db09e7cda26a…
Author: Ronny Bruska <ronny.bruska(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
A .werks/11666
M cmk/gui/plugins/config/base.py
M tests/unit/cmk/gui/test_sidebar.py
Log Message:
-----------
11666 Remove quicksearch as default sidebar snapin
CMK-5990
Change-Id: Ic9746ced9abedf8955582e9a1af34694dbb7d29f
Compare: https://github.com/tribe29/checkmk/compare/6bb65c2739c2...0df136c7f3fd
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 85c7406f5d72cdc0a4fdc5f126ecfbe7de6ab2c8
https://github.com/tribe29/checkmk/commit/85c7406f5d72cdc0a4fdc5f126ecfbe7d…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
A .werks/11752
M cmk/base/checkers/snmp.py
M cmk/base/config.py
M cmk/base/default_config/base.py
M cmk/gui/plugins/wato/check_mk_configuration.py
M cmk/gui/watolib/__init__.py
M tests/unit/cmk/gui/watolib/test_rulespecs.py
Log Message:
-----------
11752 FIX Management board: SNMP bulk walk can now be configured
SNMP Management boards were previously contacted with different SNMP settings.
SNMP management boards on non-SNMP hosts always used SNMPv1 (no bulk walk)
while SNMP management boards of hosts that are also monitored with SNMP,
inherited the bulk walk option from the host.
With Checkmk 2.0 it is now possible to explicitly configure this setting using
the ruleset "Management board SNMP using bulk walk (enforces SNMP v2c)".
Sites created with Checkmk 2.0 or newer will automatically use SNMPv2 and bulk
walks for all SNMP management boards. For compatibility reasons the behaviour
of existing sites is kept as initially described. However, in case your devices
support SNMPv2 and bulk walks, it is highly recommended to use it, for performance
reasons. In case you want to change to SNMPv2, you can create a rule without
condition in the ruleset "Management board SNMP using bulk walk (enforces SNMP
v2c)" to switch the default to SNMPv2 and bulk walks.
Change-Id: I9d80789a8ccefcbbdb4a0753f0c386e5238a517b
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: cf8cfec1f502a9124c9b932246145e1311e3402b
https://github.com/tribe29/checkmk/commit/cf8cfec1f502a9124c9b932246145e131…
Author: Timotheus Bachinger <timotheus.bachinger(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
M web/htdocs/js/modules/search.js
Log Message:
-----------
Clear search field after following result
CMK-6471
Change-Id: I9d56671200f1c531c94ad87550861bed8556e1bd
Commit: 6f01a234fe7c03a4cba53d2c06ab09262696edc5
https://github.com/tribe29/checkmk/commit/6f01a234fe7c03a4cba53d2c06ab09262…
Author: Timotheus Bachinger <timotheus.bachinger(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
A .werks/11350
Log Message:
-----------
11350 Clear search query after following result
The user's input query into the monitoring and setup search field is now getting cleared in case the result is followed by either clicking on the result or selecting it via "enter".
Change-Id: I1b89fc833c76363e9fd469a7c6971c2f8ffa2d9e
Commit: 9bfcfbbb45ceaf6b954867cb1aeaa3dd3bb2a449
https://github.com/tribe29/checkmk/commit/9bfcfbbb45ceaf6b954867cb1aeaa3dd3…
Author: Timotheus Bachinger <timotheus.bachinger(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
M web/htdocs/themes/facelift/scss/_mega_menu.scss
Log Message:
-----------
Green border for search form when focussed
CMK-6088
Change-Id: I70e464083df1a95ff424ace88776729a45185be9
Commit: 6bb65c2739c2a5c65c3c60a311deb9428dd347da
https://github.com/tribe29/checkmk/commit/6bb65c2739c2a5c65c3c60a311deb9428…
Author: Timotheus Bachinger <timotheus.bachinger(a)tribe29.com>
Date: 2020-12-07 (Mon, 07 Dec 2020)
Changed paths:
M web/htdocs/themes/facelift/scss/_dashboard.scss
M web/htdocs/themes/facelift/scss/_login.scss
M web/htdocs/themes/facelift/scss/_main.scss
M web/htdocs/themes/facelift/scss/_node_visualization.scss
M web/htdocs/themes/facelift/scss/_variables.scss
M web/htdocs/themes/modern-dark/scss/_variables.scss
Log Message:
-----------
Refactor scss color variable
* We had too many shades of green, which look all more or less the same
* Consolidate and remove superfluous definitions
Change-Id: I822094b71c38d71572a1c48dffc4d3d834668270
Compare: https://github.com/tribe29/checkmk/compare/fab42408729a...6bb65c2739c2