Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 6066d0feae5a0e0c5743b055217fb0ccea17d800
https://github.com/tribe29/checkmk/commit/6066d0feae5a0e0c5743b055217fb0cce…
Author: Sergey Kipnis <sergey.kipnis(a)tribe29.com>
Date: 2020-02-24 (Mon, 24 Feb 2020)
Changed paths:
M agents/wnx/src/engine/cap.cpp
M agents/wnx/src/engine/cap.h
M agents/wnx/src/engine/cma_core.cpp
M agents/wnx/src/engine/cma_core.h
M agents/wnx/watest/test-cap.cpp
M agents/wnx/watest/test-cma_core.cpp
Log Message:
-----------
[CMK-3803] - AreTheSame moved to the cma::tools namespace
- imporved unit testing
Change-Id: I354397e3148c906c6d25a66f6cf768a939d24f20
Branch: refs/heads/1.6.0
Home: https://github.com/tribe29/checkmk
Commit: 6aa5b0cff9d15395ce2b27786fcefcaa649f0d0f
https://github.com/tribe29/checkmk/commit/6aa5b0cff9d15395ce2b27786fcefcaa6…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2020-02-24 (Mon, 24 Feb 2020)
Changed paths:
A .werks/10862
M web/htdocs/js/modules/dashboard.js
Log Message:
-----------
10862 FIX Dashboard: Fixed "invalid dashlet coordinate" after moving dashlet in Chrome
When moving dashlets on a Checkmk dashboard while the page is zoomed to e.g. 75% in chrome,
this lead to "invalid dashlet coordinate" popup error messages.
A workaround was to change the browser zoom level to 100%, then the dashlets could be moved
as usual.
Change-Id: I06f75a61510fcded941da5c6c27ddedfbe590755
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: a5a4d71b272f4ae7cffd931a0770c043737af6dd
https://github.com/tribe29/checkmk/commit/a5a4d71b272f4ae7cffd931a0770c0437…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2020-02-24 (Mon, 24 Feb 2020)
Changed paths:
A .werks/10862
M web/htdocs/js/modules/dashboard.js
Log Message:
-----------
10862 FIX Dashboard: Fixed "invalid dashlet coordinate" after moving dashlet in Chrome
When moving dashlets on a Checkmk dashboard while the page is zoomed to e.g. 75% in chrome,
this lead to "invalid dashlet coordinate" popup error messages.
A workaround was to change the browser zoom level to 100%, then the dashlets could be moved
as usual.
Change-Id: I06f75a61510fcded941da5c6c27ddedfbe590755
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 8d45ea89642b6a7b6dcc904a30fe6e97deaf31d1
https://github.com/tribe29/checkmk/commit/8d45ea89642b6a7b6dcc904a30fe6e97d…
Author: Tom Baerwinkel <tom.baerwinkel(a)tribe29.com>
Date: 2020-02-24 (Mon, 24 Feb 2020)
Changed paths:
A .werks/10747
M checks/ibm_svc_mdisk
A tests/unit/checks/generictests/datasets/ibm_svc_mdisk_regression_2.py
Log Message:
-----------
10747 FIX ibm_svc_mdisk: don't crash on discovery
On devices that do not support the lsmdisk command the check plugin
ibm_svc_mdisk failed so that the "Check_MK Discovery" service showed
the error "UNKN - check failed - please submit a crash report!".
This is fixed.
Change-Id: I8a8992446522c63a74ed8464d4ad200c511f9621
Branch: refs/heads/1.6.0
Home: https://github.com/tribe29/checkmk
Commit: 2bc8d2a9a6d9e6c00f3560ab0cb7e11dc308fc98
https://github.com/tribe29/checkmk/commit/2bc8d2a9a6d9e6c00f3560ab0cb7e11dc…
Author: Tom Baerwinkel <tom.baerwinkel(a)tribe29.com>
Date: 2020-02-24 (Mon, 24 Feb 2020)
Changed paths:
A .werks/10747
M checks/ibm_svc_mdisk
A tests/unit/checks/generictests/datasets/ibm_svc_mdisk_regression_2.py
Log Message:
-----------
10747 FIX ibm_svc_mdisk: don't crash on discovery
On devices that do not support the lsmdisk command the check plugin
ibm_svc_mdisk failed so that the "Check_MK Discovery" service showed
the error "UNKN - check failed - please submit a crash report!".
This is fixed.
Change-Id: I8a8992446522c63a74ed8464d4ad200c511f9621
Branch: refs/heads/1.6.0
Home: https://github.com/tribe29/checkmk
Commit: 458dbf82f2c5aaa6b72ba7f8704d4f692eaa329c
https://github.com/tribe29/checkmk/commit/458dbf82f2c5aaa6b72ba7f8704d4f692…
Author: Andreas Boesl <andreas.boesl(a)tribe29.com>
Date: 2020-02-24 (Mon, 24 Feb 2020)
Changed paths:
A .werks/10529
Log Message:
-----------
10529 FIX Checkmk RRD helper: fixed exception when creating new rrd files
The Checkmk RRD helper is used whenever the microcore tries to create a new rrd file.
During this process the RRD helper tries to parse the autochecks file for the host in question.
In some instances, the autochecks file referred to variables defined within checks.
This caused RRD to silently crash without parsing the content of the autochecks file.
In most instances this had no negative effect.
However, the recently introduced labels might be incorrectly computed because of the missing autochecks file content.
WATO configured RRD rules which rely on labels might be affected by this bug (but only when creating new rrd files).
Change-Id: I481879e9bf09560304b814b8d9f43d5c5203c3fa
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 477fba2cd582f2657b7f525b016651282bafda2b
https://github.com/tribe29/checkmk/commit/477fba2cd582f2657b7f525b016651282…
Author: Lukas Lengler <lukas.lengler(a)tribe29.com>
Date: 2020-02-24 (Mon, 24 Feb 2020)
Changed paths:
M checkman/aws_costs_and_usage
M checkman/aws_costs_and_usage.per_service
M checkman/aws_ebs
M checkman/aws_ebs.burst_balance
M checkman/aws_ebs_summary.health
M checkman/aws_ec2.disk_io
M checkman/aws_ec2.network_io
M checkman/aws_glacier
M checkman/aws_rds
M checkman/aws_rds.agent_jobs
M checkman/aws_rds.bin_log_usage
M checkman/aws_rds.connections
M checkman/aws_rds.cpu_credits
M checkman/aws_rds.disk_io
M checkman/aws_rds.network_io
M checkman/aws_rds.replica_lag
M checkman/aws_rds.replication_slot_usage
M checkman/aws_rds.transaction_logs_usage
M checkman/aws_rds_summary.db_status
M checkman/aws_s3
M checkman/aws_s3_requests
M checkman/aws_s3_requests.http_errors
M checkman/aws_s3_requests.latency
M checkman/aws_s3_requests.select_object
M checkman/aws_s3_requests.traffic_stats
Log Message:
-----------
Added/Changed item entries for manpages (aws)
Change-Id: I5b9a4912d5aa0503ab41b3fd3770abf91b2ef7c3
Commit: 50615cf5d88ed139967ed621fea3d6553ef4cd4e
https://github.com/tribe29/checkmk/commit/50615cf5d88ed139967ed621fea3d6553…
Author: Lukas Lengler <lukas.lengler(a)tribe29.com>
Date: 2020-02-24 (Mon, 24 Feb 2020)
Changed paths:
M checkman/cisco_asa_failover
M checkman/cisco_cpu_memory
M checkman/cisco_cpu_multiitem
M checkman/cisco_ip_sla
M checkman/cisco_mem
M checkman/cisco_mem_asa
M checkman/cisco_mem_asa64
M checkman/cisco_ucs_cpu
M checkman/cisco_ucs_fan
M checkman/cisco_ucs_hdd
M checkman/cisco_ucs_mem
M checkman/cisco_ucs_psu
M checkman/cisco_wlc
Log Message:
-----------
Added/Changed item entries for manpages (cisco*)
Change-Id: I0e474a19852eb9a3ac9b0fccea2bb1564696ed38
Commit: da73b5f17f7865706f4da215b31bf4e33ae8c00b
https://github.com/tribe29/checkmk/commit/da73b5f17f7865706f4da215b31bf4e33…
Author: Andreas Boesl <andreas.boesl(a)tribe29.com>
Date: 2020-02-24 (Mon, 24 Feb 2020)
Changed paths:
A .werks/10529
Log Message:
-----------
10529 FIX Checkmk RRD helper: fixed exception when creating new rrd files
The Checkmk RRD helper is used whenever the microcore tries to create a new rrd file.
During this process the RRD helper tries to parse the autochecks file for the host in question.
In some instances, the autochecks file referred to variables defined within checks.
This caused RRD to silently crash without parsing the content of the autochecks file.
In most instances this had no negative effect.
However, the recently introduced labels might be incorrectly computed because of the missing autochecks file content.
WATO configured RRD rules which rely on labels might be affected by this bug (but only when creating new rrd files).
Change-Id: I481879e9bf09560304b814b8d9f43d5c5203c3fa
Compare: https://github.com/tribe29/checkmk/compare/c5b15f521824...da73b5f17f78