-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
update integer output to new line protocol format #99
Comments
influxdata/influxdb#3589 for the relevant issue |
To summarize an email thread, this will simply require a re-build of telegraf using the 0.9.3 release of InfluxDB. Currently the head of influxdb will not work with telegraf unless you build it from source. |
closing this out because it should be fixed with any newer build of telegraf |
@sparrc is there a plan to issue new telegraf builds in conjunction with new influxdb builds? |
@beckettsean Not at the moment, but the CircleCI job is now building binaries as well as .deb and .rpm files, so one can find an updated package there if need be https://circleci.com/gh/influxdb/telegraf/tree/master I believe that it was decided that Telegraf would release on it's own schedule unless there was a release of another product (such as InfluxDB) that introduced a breaking change. |
@sparrc I agree with and support the decision about releases in general, but this issue was about a specific case of the "breaking change" mentioned. I would like to know that we will have a coordinated release of telegraf and InfluxDB with the integer write change. An issue seems like a good place to track that so we don't forget on launch day. |
@beckettsean fair enough, I'll keep it open |
This is fixed and ready in 0.1.5 |
With 0.9.3, the line protocol has changed for integers: influxdata/influxdb#3526
This change means that current telegraf users who upgrade to 0.9.3 cannot write a number of values, because they are integer fields in the db but the current telegraf sends them without the trailing
i
, meaning they parse as floats. That causes a type mismatch and a write failure.The text was updated successfully, but these errors were encountered: