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

input_zookeeper sends empty server tag #4381

Closed
dimas opened this issue Jul 4, 2018 · 0 comments
Closed

input_zookeeper sends empty server tag #4381

dimas opened this issue Jul 4, 2018 · 0 comments
Assignees
Labels
bug unexpected problem or unintended behavior
Milestone

Comments

@dimas
Copy link

dimas commented Jul 4, 2018

Relevant telegraf.conf:

[[inputs.zookeeper]]
  servers = [":2181"]

System info:

Linux ip-10-0-158-207 3.13.0-149-generic #199-Ubuntu SMP Thu May 17 10:12:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
ii  telegraf                                  1.6.2-1                                    amd64        Plugin-driven server agent for reporting metrics into InfluxDB.

Expected behavior:

The https://github.com/influxdata/telegraf/tree/master/plugins/inputs/zookeeper page says

  ## If no servers are specified, then localhost is used as the host.
  ## If no port is specified, 2181 is used

Actual behavior:

Metrics do get collected as expected however server tag is reported as an empty string which causes problem down the line for us. At the same time, if we set servers as "localhost:2181" instead of just ":2181" the same metrics are collected and server="localhost" tag is reported.

While problems caused by an empty tag are specific to our metric ingestion chain, it is a bit misleading that docs say no server is the same as localhost but in reality there is a difference.

To be honest I am not sure myself if this issue really worth fixing, just reporting you a discrepancy we came across.

@glinton glinton added the bug unexpected problem or unintended behavior label Jul 5, 2018
@glinton glinton self-assigned this Jul 5, 2018
glinton added a commit that referenced this issue Jul 5, 2018
@danielnelson danielnelson added this to the 1.7.2 milestone Jul 5, 2018
This issue was closed.
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

No branches or pull requests

3 participants