diff --git a/CHANGELOG.md b/CHANGELOG.md index 6cd184d149314..c5d16c9d5fd01 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,7 @@ [#112](://github.com/influxdb/telegraf/pull/112): Datadog output. Thanks @jipperinbham! ### Bugfixes +[113](https://github.com/influxdb/telegraf/issues/113): Update README with Telegraf/InfluxDB compatibility ## v0.1.5 [2015-08-13] @@ -30,6 +31,7 @@ - [#89](https://github.com/influxdb/telegraf/pull/89): go fmt fixes - [#94](https://github.com/influxdb/telegraf/pull/94): Fix for issue #93, explicitly call sarama.v1 -> sarama - [#101](https://github.com/influxdb/telegraf/issues/101): switch back from master branch if building locally +- [#99](https://github.com/influxdb/telegraf/issues/99): update integer output to new InfluxDB line protocol format ## v0.1.4 [2015-07-09] diff --git a/README.md b/README.md index 8074e59402bec..ff98543beb1d4 100644 --- a/README.md +++ b/README.md @@ -23,10 +23,19 @@ agent is NOT backwards-compatible with a config file from 0.1.4 and below. That being said, the difference is not huge, see below for an example on how to setup the new config file. -``` -http://get.influxdb.org/telegraf/telegraf_0.1.5_amd64.deb -http://get.influxdb.org/telegraf/telegraf-0.1.5-1.x86_64.rpm -``` +As well, due to a breaking change to the InfluxDB integer line-protocol, there +are some InfluxDB compatibility requirements: + +* InfluxDB 0.9.3+ (including nightly builds) requires Telegraf 0.1.5+ +* InfluxDB 0.9.2 and prior requires Telegraf 0.1.4 + +Telegraf 0.1.5 +* http://get.influxdb.org/telegraf/telegraf_0.1.5_amd64.deb +* http://get.influxdb.org/telegraf/telegraf-0.1.5-1.x86_64.rpm + +Telegraf 0.1.4 +* http://get.influxdb.org/telegraf/telegraf_0.1.4_amd64.deb +* http://get.influxdb.org/telegraf/telegraf-0.1.4-1.x86_64.rpm ### OSX via Homebrew: @@ -79,7 +88,7 @@ you can configure that here. ### Plugin Configuration Examples This is a full working config that will output CPU data to an InfluxDB instance -at 192.168.59.103:8086, tagging measurements with dc="Denver-1". It will output +at 192.168.59.103:8086, tagging measurements with dc="denver-1". It will output measurements at a 10s interval and will collect totalcpu & percpu data. ``` [outputs]