-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Comments
this behavior was changed for consistency. A workaround would be for your kafka_consumer telegraf instance to use the |
But then what about the measurements the kafka_consumer telegraf instance generates by itself from its other inputs (cpu, memory, etc.) ? |
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. |
Please, include this fix in the next point release. |
you can view the release it will be on in the changelog |
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.
The text was updated successfully, but these errors were encountered: