telegraf

telegraf:release-1.2

  1. Git
  2. lp:telegraf
  3. release-1.2
Last commit made on 2017-02-01
Get this branch:
git clone -b release-1.2 https://git.launchpad.net/telegraf

Branch merges

Branch information

Name:
release-1.2
Repository:
lp:telegraf

Recent commits

3b6ffb3... by Cameron Sparr

Go 1.7.4 -> 1.7.5

c9d359f... by Cameron Sparr

metric: Fix negative number handling

closes #2324

45ea321... by Cameron Sparr

running output: Drop nil metrics

fixes #2317

853178c... by Cameron Sparr

32-bit binary for windows and freebsd

closes #1346
closes #2218

b2c1d98... by Cameron Sparr

empty commit for tagging release 1.2

10d0a78... by Cameron Sparr

influxdb output: treat field type conflicts as a successful write

If we write a batch of points and get a "field type conflict" error
message in return, we should drop the entire batch of points because
this indicates that one or more points have a type that doesnt match the
database.

These errors will never go away on their own, and InfluxDB will
successfully write the points that dont have a conflict.

closes #2245

8282311... by Cameron Sparr

Add newline to influx line-protocol if not present

closes #2297

c3ae757... by Cameron Sparr

opentsdb: add tcp:// prefix if not present

closes #2299

95bad9e... by Cameron Sparr

OpenTSDB filter types for HTTP AND telnet

e812a2e... by Cameron Sparr <email address hidden>

Accept an HTTP request body without newline at end (#2266)

I don't like this behavior, but it's what InfluxDB accepts, so the
telegraf listener should be consistent with that.

I accidentally reverted this behavior when I refactored the telegraf
metric representation earlier in this release cycle.