> It seems InfluxDB http requests automatically casts measurements in
millis to nanos
InfluxDB does not automatically cast timestamps. How are you writing your
points?
$ curl -XPOST 'http://localhost:8086/write?db=test' --data-binary 'foo
bar="NOT using precision=ms" 1484346119541'
$ curl -XPO
Hi,
Looks like Kapacitor uses a pub/sub interface for influxdb, to get
notifications. This is the module responsible for it, i think
(https://github.com/influxdata/influxdb/tree/master/services/subscriber).
Was wondering if there is an existing python binding for the subscriber
module?
My
OK, I narrowed it down to the source of the metrics. It seems InfluxDB http
requests automatically casts measurements in millis to nanos, but when
passed through a Telegraf proxy this doesn't happen.
Good to know it's not a bug, but just something that goes against the principle
of least astoni
OS:
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename: xenial
InfluxDB shell version: 1.1.1
Influx inputs:
tcp6 0 0 [::]:8086 [::]:*
LISTEN 19433/influxd
tcp6 0 0 [::]:omniorb[::]:
The telegraf 1.2.0-rc1 Dockerfile was just merged into influxdata-docker
two hours ago :) https://github.com/influxdata/influxdata-docker/pull/52
On Fri, Jan 13, 2017 at 9:57 AM, Jaka Hudoklin
wrote:
> Hi,
>
> Will docker image or deb packages for telegraf-1.2.0-rc1 be released
> anytime soon(in
Hi,
Will docker image or deb packages for telegraf-1.2.0-rc1 be released
anytime soon(in a week timeline)? I would like to know, so i can plan if i
do need to make my own telegraf docker image building from source.
Best regards, Jaka!
--
Remember to include the version number!
---
You receiv
Could you provide your Telegraf configuration? Also what version of
Telegraf are you using?
On Fri, Jan 13, 2017 at 9:20 AM, Niels van Klaveren <
niels.vanklave...@gmail.com> wrote:
> When metrics are sent to Telegraf's http-input plugin and from there sent
> to InfluxDB, the nanosecond timestamp
When metrics are sent to Telegraf's http-input plugin and from there sent
to InfluxDB, the nanosecond timestamps are truncated by removing the last 9
0's. This means all timestamps in InfluxDB end up in the far past instead
of the correct time.
The same values sent straight to InfluxDB are corr
