19 Jun
2019
19 Jun
'19
4:20 a.m.
Branch: refs/heads/1.5.0
Home: https://github.com/tribe29/checkmk
Commit: 2a9b07d13d447cceeab8c54e4262172e72e442ed
https://github.com/tribe29/checkmk/commit/2a9b07d13d447cceeab8c54e4262172e7…
Author: Simon Jess <simon.jess(a)tribe29.com>
Date: 2019-06-19 (Wed, 19 Jun 2019)
Changed paths:
A .werks/7833
M checks/mongodb_flushing
M web/plugins/metrics/check_mk.py
Log Message:
-----------
7833 FIX mongodb_flushing: Fixed scaling and missing titles for performance values
'Flush time', '#Flushes' and 'Average flush time'
Change-Id: Iac21f3096ba982bbab4d0753c1a1863146c6c3b5
Commit: 4be18c1e2033ab569c93594d06daa18c2278c419
https://github.com/tribe29/checkmk/commit/4be18c1e2033ab569c93594d06daa18c2…
Author: Tom Baerwinkel <tom.baerwinkel(a)tribe29.com>
Date: 2019-06-19 (Wed, 19 Jun 2019)
Changed paths:
A .werks/7423
M agents/plugins/mk_postgres
Log Message:
-----------
7423 FIX mk_postgres: fix syntax error
Version 1.5.0p17 and 1.5.0p18 of the mk_postgres plugin gave a
syntax error when parsing databases. This results in empty
output between [databases_start] and [databases_end] in the
plugin output. As a consequence the checks postgres_stats,
postgres_bloat, postgres_connections, postgres_locks and
postgres_query_duration become stale.
To resolve the error the fixed version of mk_postgres has to be
deployed to the affected hosts.
Change-Id: I8dc5e88e3a7584538f2ba09407c54a27a1837ca4
Commit: 51f5913597232b8bcd16f2fa3fa805fdd337410d
https://github.com/tribe29/checkmk/commit/51f5913597232b8bcd16f2fa3fa805fdd…
Author: Tom Baerwinkel <tom.baerwinkel(a)tribe29.com>
Date: 2019-06-19 (Wed, 19 Jun 2019)
Changed paths:
A .werks/7424
M agents/plugins/mk_postgres
Log Message:
-----------
7424 FIX mk_postgres: add missing database parameter
The mk_postgres plugin was missing a database parameter in
the queries for the checks postgres_bloat and postgres_stats.
Therefore, the name of the database user was used as a
fallback. As a result no output for postgres_stats and
postgres_bloat was returned if a database with the username
did not exist. If a database with the username exists
the checks give the correct output.
To resolve the issue the fixed version of the mk_postgres
plugin has to be deployed on the affected hosts.
Change-Id: I1df8e3e52184c86dff7e2335e29639079fd69bc1
Commit: 15f06c84afb87862f5d452f8d03a39b978ba3d8f
https://github.com/tribe29/checkmk/commit/15f06c84afb87862f5d452f8d03a39b97…
Author: Tom Baerwinkel <tom.baerwinkel(a)tribe29.com>
Date: 2019-06-19 (Wed, 19 Jun 2019)
Changed paths:
A .werks/7426
M agents/plugins/mk_postgres
Log Message:
-----------
7426 FIX mk_postgres: fix the version detection when using an MK_CONFFILE
Since version 1.5.0p17 the version detection fails if an MK_CONFFILE
is used and the psql binary cannot be found in the PATH. To resolve
the issue the fixed version of the mk_postgres plugin has to be
deployed on the affected hosts.
Change-Id: Idd16c018c62b2893b45189a94b95df94bdcda472
Compare: https://github.com/tribe29/checkmk/compare/3c22306c1370...15f06c84afb8