You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Michał Lisowski (Jira)" <ji...@apache.org> on 2020/03/25 12:47:00 UTC
[jira] [Updated] (ZOOKEEPER-3770) Monitoring script support for 3.6
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michał Lisowski updated ZOOKEEPER-3770:
---------------------------------------
Affects Version/s: (was: 3.5.3)
> Monitoring script support for 3.6
> ---------------------------------
>
> Key: ZOOKEEPER-3770
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3770
> Project: ZooKeeper
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 3.6.0, 3.6.1, 3.6.2
> Environment: OS: Red Hat Enterprise Linux Server release 7.7
> Zookeeper version: 3.6.0
> Python version: 2.7.5
> Reporter: Michał Lisowski
> Priority: Minor
> Fix For: 3.6.0, 3.6.1, 3.6.2
>
>
> The zookeeper-contrib-monitoring script needs fixes to support zookeeper 3.6.
> Found issues:
> * 4lw.commands.whitelist=mntr,ruok,stat is now required for the script to work, as 4 letter words commands are now all disabled by default (README has to be updated).
> * zk_avg_latency metric is now float, the script has them all as strings anyway, and now it fails when trying to compare for example the '0.0' string to the warning and critical values.
> * Now, since 'mntr' command returns much more data (even more with the Prometheus Metrics Exporter), python socket communication has to be changed to support much more data and data chunking.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)