Cameron Sparr 819813ad72 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		2017-01-23 16:41:29 -08:00
..
all	…
amon	Major Logging Overhaul	2016-10-03 17:13:03 +01:00
amqp	…
cloudwatch	…
datadog	Major Logging Overhaul	2016-10-03 17:13:03 +01:00
discard	…
file	file output plugin fixup	2016-12-02 11:36:22 +00:00
graphite	…
graylog	Graylog output should set short_message field	2016-12-13 16:10:59 +00:00
influxdb	influxdb output: treat field type conflicts as a successful write	2017-01-23 16:41:29 -08:00
instrumental	Fix unit tests for new metric implementation	2016-12-01 18:17:02 +00:00
kafka	…
kinesis	Moved to using the inbuilt serializer. (#1942)	2016-12-20 18:49:28 +00:00
librato	…
mqtt	Enable setting a clientID for MQTT Output	2016-12-13 20:03:09 +00:00
nats	Implement telegraf's own full metric type	2016-12-01 18:17:02 +00:00
nsq	Implement telegraf's own full metric type	2016-12-01 18:17:02 +00:00
opentsdb	opentsdb: add tcp:// prefix if not present	2017-01-23 13:45:16 -08:00
prometheus_client	…
riemann	…
registry.go	…