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

Elasticsearch Metrics are not correctly parsed/emitted to OpenTSDB #4675

Closed
langerma opened this issue Sep 11, 2018 · 5 comments
Closed

Elasticsearch Metrics are not correctly parsed/emitted to OpenTSDB #4675

langerma opened this issue Sep 11, 2018 · 5 comments
Labels
area/elasticsearch bug unexpected problem or unintended behavior regression something that used to work, but is now broken
Milestone

Comments

@langerma
Copy link

langerma commented Sep 11, 2018

Relevant telegraf.conf:

[agent]
  interval = "10s"
  round_interval = true
  metric_batch_size = 100
  metric_buffer_limit = 4000000
  collection_jitter = "0s"
  flush_interval = "10s"
  flush_jitter = "0s"
  precision = ""
  debug = false
  quiet = false
  hostname = ""
  omit_hostname = false

[[outputs.opentsdb]]
   host = "http://127.0.0.1"
   port = 14242
   httpBatchSize = 100

[[inputs.elasticsearch]]
   servers = ["http://localhost:9200"]
   http_timeout = "5s"
   local = true
   cluster_health = true
   cluster_stats = true

System info:

telegraf-1.7.4-1.x86_64.rpm / RHEL 7 / Elasticsearch 6.4

Steps to reproduce:

  1. install telegraf 1.7.4-1
  2. restart telegraf

Expected behavior:

same config works with telegraf 1.5.3-1.x86_64.rpm everything works fine

Actual behavior:

10:16:10.310 WARN [PutDataPointRpc.execute] - Invalid tag value: empty string: metric=elasticsearch_clusterstats_indices_segments_count ts=1536653770 value=12156 cluster_name=george-visualisation environment=PROD host=gevismasterp1at.eb.lan.at node_name= status=green

this error is the same for all clusterstats metrics.

@glinton glinton added bug unexpected problem or unintended behavior area/elasticsearch labels Sep 11, 2018
@glinton
Copy link
Contributor

glinton commented Sep 11, 2018

Thanks for the report.

@langerma
Copy link
Author

any updates on this issue?

@danielnelson danielnelson added the regression something that used to work, but is now broken label Sep 24, 2018
@danielnelson danielnelson added this to the 1.8.1 milestone Sep 24, 2018
@glinton
Copy link
Contributor

glinton commented Sep 24, 2018

@langerma did you update your version of opentsdb or another part of your stack while updating to telegraf 1.7.4? Nothing really changed in the tsdb output since 1.5.3 and I wasn't able to find anywhere in the elastic input plugin that would cause the node_name to be empty. I'm continuing to investigate however.

screenshot from 2018-09-24 17-19-29

@langerma
Copy link
Author

no i did no update...neither on opentsdb side nor elastic side. i guess it is a problem with the elastic input.

@langerma
Copy link
Author

thx, will try once the new telegraf version is released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/elasticsearch bug unexpected problem or unintended behavior regression something that used to work, but is now broken
Projects
None yet
Development

No branches or pull requests

3 participants