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

Kafka consumer overwriting host tag #1210

Closed
dvenza opened this issue May 17, 2016 · 5 comments · Fixed by #1228
Closed

Kafka consumer overwriting host tag #1210

dvenza opened this issue May 17, 2016 · 5 comments · Fixed by #1228
Labels
bug unexpected problem or unintended behavior

Comments

@dvenza
Copy link

dvenza commented May 17, 2016

I have a setup where I have several telegraf processes sending data to Kafka via the Kafka output. Then I have one telegraf instance that uses the kafka input to consume the measurements and store them in influxdb.

Since telegraf 0.13 all my measurements have the wrong "host" tag, they seem to be coming from the host that runs the kafka consumer.

This is a big issue for me: telegraf 0.12 crashed every time a new container was spawned in Docker, so I do not want to downgrade, but with 0.13 all my monitoring and dashboards are useless.

@sparrc sparrc added bug unexpected problem or unintended behavior and removed bug unexpected problem or unintended behavior labels May 17, 2016
@sparrc
Copy link
Contributor

sparrc commented May 17, 2016

this behavior was changed for consistency. A workaround would be for your kafka_consumer telegraf instance to use the omit_hostname config option (see https://github.com/influxdata/telegraf/blob/master/etc/telegraf.conf#L62)

@dvenza
Copy link
Author

dvenza commented May 17, 2016

But then what about the measurements the kafka_consumer telegraf instance generates by itself from its other inputs (cpu, memory, etc.) ?
They are sent without any host tag?

@sparrc
Copy link
Contributor

sparrc commented May 17, 2016

correct, they wouldn't, this is an unintended consequence of implementing #1054, so I would say it's a bug and I should revert part of that change.

@sparrc sparrc added the bug unexpected problem or unintended behavior label May 17, 2016
sparrc added a commit that referenced this issue May 19, 2016
sparrc added a commit that referenced this issue May 19, 2016
sparrc added a commit that referenced this issue May 19, 2016
@dvenza
Copy link
Author

dvenza commented May 19, 2016

Please, include this fix in the next point release.

@sparrc
Copy link
Contributor

sparrc commented May 19, 2016

you can view the release it will be on in the changelog

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