Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zookeeper: when no servers specified, doesn't collect statistics #2886

Closed
smalenfant opened this issue Jun 5, 2017 · 0 comments · Fixed by #3056
Closed

zookeeper: when no servers specified, doesn't collect statistics #2886

smalenfant opened this issue Jun 5, 2017 · 0 comments · Fixed by #3056
Labels
bug unexpected problem or unintended behavior
Milestone

Comments

@smalenfant
Copy link

Directions

Bug report

Enable the input only with [[inputs.zookeeper]] doesn't collect any statistics

Relevant telegraf.conf:

[[inputs.zookeeper]]

System info:

Centos 7.3, telegraf 1.2.1

Steps to reproduce:

telegraf --test --config /etc/telegraf/telegraf.conf --config-directory /etc/telegraf/telegraf.d --input-filter zookeeper

Expected behavior:

Input to provide collection for zookeeper on localhost when there is no servers specified.

Actual behavior:

[root@zookeeper01~]# telegraf --test --config /etc/telegraf/telegraf.conf --config-directory /etc/telegraf/telegraf.d --input-filter zookeeper
* Plugin: inputs.zookeeper, Collection 1

Additional info:

Proposal:

Current behavior:

According to documentation (at least the way I read it), servers parameter seems optional and would use localhost:2181.

Desired behavior:

With simple input configured, zookeeper collection would start on localhost. This is what most input plugins works.

Use case: [Why is this important (helps with prioritizing requests)]

Workaround is fairly easy, specify servers = [":2181"]

@danielnelson danielnelson added the bug unexpected problem or unintended behavior label Jun 5, 2017
@danielnelson danielnelson added this to the 1.4.0 milestone Jun 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants