-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timestamp not parsing seconds correctly #10234
Comments
Can you please provide the actual output that shows it off by 2 seconds? I am not seeing the same thing:
Then convert the timestamp to a real date:
edit: if you could run this with |
@powersj I am new to influx db, so I am not sure what commands I need to use to get the results in the form you expect them, but here are some screenshots (we are using Influx Cloud): Also, others seem to have had a similar problem, (#4928 (comment)) maybe related? |
That top screenshot's timestamp format is not what you showed in your original comment. In the post on the community forum and the initial post you showed:
But that 2nd screenshot shows:
So yes, you will need to set the timestamp format correctly. |
@powersj my bad, I was testing all possibilities. The result is the same, independently of the input. The result is the same, in particular the UI in Influx cloud seems to always set seconds to 10 and ms to 000 (you can see that also all the previous times have sec == 10 and ms == 000) In other words, the problem occurs both with 2021-12-07T14:56:02Z and 2021-12-07T14:56:02.123Z formats. |
ok so something is happening between when you read the data and when you see it in InfluxDB. Can you remove InfluxDB from the equation, and run telegraf independently by running with the |
@powersj I think it's a bug in the influx cloud UI (I mean in the Influx explorer). In fact, I have read the data via influx cli, and the timestamps seem to be picked up correctly, with seconds and ms showing just fine. |
Awesome, thanks for confirming! If you could file a bug with InfluxDB UI here I would appreciate it. I'm going to go ahead and close this. |
Coming from https://community.influxdata.com/t/timestamp-not-being-recorded-json-v2/22818/6
Relevent telegraf.conf
System info
Linux 4.15.0-163-generic Ubuntu; Telegraf 1.20.4 (git: HEAD 34ad5aa)
Docker
No response
Steps to reproduce
The text was updated successfully, but these errors were encountered: