Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Non-uniform timestamp format between querying and writing

See original GitHub issue

I was trying to use queryRaw to do some data migration, and found that a point retrieved via .queryRaw isn’t easily passed to .writePoint.

queryRaw (and query as well) pass through the JSON returned by Influx, which serializes dates into RFC3339 strings.

The problem is that .writePoints expects a Date object or a UNIX time.

Issue Analytics

State:
Created 7 years ago
Comments:7 (6 by maintainers)

Top GitHub Comments

1reaction

dandvcommented, Oct 7, 2016

Also good to know about the time format in responses, since this may help optimize parsing:

Everything in InfluxDB is stored and reported in UTC. By default, timestamps are returned in RFC3339 UTC and have nanosecond precision, for example 2015-08-04T19:05:14.318570484Z. If you want timestamps in Unix epoch format include in your request the query string parameter epoch where epoch=[h,m,s,ms,u,ns]. For example, get epoch in seconds with:

curl -G 'http://localhost:8086/query' --data-urlencode "db=mydb" --data-urlencode "epoch=s" --data-urlencode "q=SELECT \"value\" FROM \"cpu_load_short\" WHERE \"region\"='us-west'"

Some libraries (e.g. HighCharts) require timestamps in UNIX format, so no parsing would be required.

1reaction

dandvcommented, Oct 7, 2016

Some docs on the (non)idempotence of timestamps would be useful.