Wrong Imported Timestamps in Chronograf

1

Hi,

iam currently trying to import old values but the timestamp is not correct.

This Timestamp 1588221453 should be 2020-04-30 06:37:33.004826
The date is correct in Influx but the time 6:12.

1574083831 should be Monday, 18. November 2019 14:30:31 but is shown as 14:25

I have imported via API to use seconds as precision but its the same whith nanosecond converted timestamps.
Adding entrys without timestamps gives the current correct time.

Any Ideas?

2

Hi,

iam currently trying to import old values but the timestamp is not correct.

This Timestamp 1588221453 should be 2020-04-30 06:37:33.004826

If you’re in UTC+2 timezone, yes (without the decimal seconds).

The date is correct in Influx but the time 6:12.

How do you get this result? How can we reproduce this answer? What query is
needed to get the time 06:12?

1574083831 should be Monday, 18. November 2019 14:30:31

For UTC+1, agreed.

but is shown as 14:25

Again, how can we reproduce this? Tell us what commands you are running so we
can see how you get these values.

I have imported via API to use seconds as precision but its the same whith
nanosecond converted timestamps. Adding entrys without timestamps gives
the current correct time.

I’m slightly bothered that you are referring to UTC+1 or UTC+2 timezones.

Almost all uses of InfluxDB require that the timestamps are in UTC, and you
need to bear that in mind when talking about what “actual time” the timestamp
represents.

That has nothing to do with offsets of a few minutes, however.

Regards,

Antony.

3

I imported it via webinterface and with
curl -i -XPOST “http://ip:8086/write?db=testdb&precision=s” --data-binary @test.txt

And is the offset of the few minutes that is bothering me.

4

Okay, so that’s how you put the data in. Thanks.

How can we reproduce the answer you get? What query is needed to get the time
06:12 out again?

Antony.

5

I just tested it with this query inside the txt file:
h,entity_id=history value=155.45 1589048429

It should be 06:37:33 but it shows me 6:00. Date is correct but not the time.

6

I’m sorry. I obviously have not expressed myself sufficiently clearly.

Please give us step-by-step instructions such as “type the following” in order
to reproduce your problem, so that we can see for ourselves what is going on.

Give us enough details so that we know exactly what to do on our own computers
to get the same result as you do.

Otherwise you are just telling us “I have the following data, and I do
something, and get the following result”.

Tell us exactly what the “something” is.

Antony.

7

Ok, sure.

  1. Open Chronograf and click on Write Data
  2. Choose Manual Entry
  3. type: t,entity_id=history value=355.45 1573338211000000000
  4. Select Date Picker and select 9. November 2019
  5. See that the imported data shows 2019/11/09 23:20 instead of 2019/11/09 23:23:31

Maybe iam missing something here, or totaly missunderstood something or maybe its just a visual bug. I used Epoch Converter to check the timestamp and it was always correct there.

8

No Ideas? Could you reproduce it?

9

Bump with at least 20 characters

10

I tried to reproduced but was unable. My version Chronograf is a bit out of date, 1.7.3.

> precision rfc3339
> select * from t
name: t
time                 entity_id value
----                 --------- -----
2019-11-09T22:23:31Z history   355.45
11

How does you it look like inside the webui?

12

The dates are correct in the DB and Grafana. Seems to be a visual bug in Chronograf.
So this issue is solved for me :smile:

13

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.