Skip to content
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

InfluxDB Timestamp #2672

Closed
Reinhard-M opened this issue Oct 29, 2023 · 4 comments · Fixed by #2679
Closed

InfluxDB Timestamp #2672

Reinhard-M opened this issue Oct 29, 2023 · 4 comments · Fixed by #2679
Assignees
Labels
bug Something isn't working

Comments

@Reinhard-M
Copy link

The Problem

Der berechnete InfluxDB Timestamp entspricht der Sommerzeit (+0200), nicht der angegebenen Winterzeit (+0100):

[0d00h01m51s] 2023-10-29T13:34:44 [INFLUXDB] Use handover timestamp: 2023-10-29T13:34:16+0100 converted GMT timestamp: 1698579256

Wenn ich den angegebenen Timestamp auf https://www.unixtimestamp.com/ eingebe kommt als Ergebnis:
Sun Oct 29 2023 12:34:16 GMT+0100 (Mitteleuropäische Normalzeit)

Version

Release: v15.3.0 (Commit: 3fbff0a)

Logfile

[0d00h01m51s] 2023-10-29T13:34:44 <DBG> [INFLUXDB] InfluxDBPublish - Key: value, Content: 29386.348, Timestamp: 2023-10-29T13:34:16+0100
[0d00h01m51s] 2023-10-29T13:34:44 <DBG> [INFLUXDB] Use handover timestamp: 2023-10-29T13:34:16+0100 converted GMT timestamp: 1698579256
[0d00h01m51s] 2023-10-29T13:34:44 <INF> [INFLUXDB] sending line to influxdb:Menge value=29386.348 1698579256000000000
[0d00h01m51s] 2023-10-29T13:34:44 <DBG> [INFLUXDB] client is initialized
[0d00h01m51s] 2023-10-29T13:34:44 <DBG> [INFLUXDB] header is set
[0d00h01m51s] 2023-10-29T13:34:44 <DBG> [INFLUXDB] post payload is set
[0d00h01m51s] 2023-10-29T13:34:44 <DBG> [INFLUXDB] HTTP Client connected
[0d00h01m51s] 2023-10-29T13:34:44 <DBG> [INFLUXDB] HTTP Client sent all request headers
[0d00h01m51s] 2023-10-29T13:34:44 <DBG> [INFLUXDB] Header: key=Content-Type, value=application/json
[0d00h01m51s] 2023-10-29T13:34:45 <DBG> [INFLUXDB] Header: key=Request-Id, value=8a507888-7657-11ee-8027-dca63261c5ab
[0d00h01m51s] 2023-10-29T13:34:45 <DBG> [INFLUXDB] Header: key=X-Influxdb-Build, value=OSS
[0d00h01m51s] 2023-10-29T13:34:45 <DBG> [INFLUXDB] Header: key=X-Influxdb-Version, value=1.8.10
[0d00h01m51s] 2023-10-29T13:34:45 <DBG> [INFLUXDB] Header: key=X-Request-Id, value=8a507888-7657-11ee-8027-dca63261c5ab
[0d00h01m51s] 2023-10-29T13:34:45 <DBG> [INFLUXDB] Header: key=Date, value=Sun, 29 Oct 2023 12:34:45 GMT
[0d00h01m51s] 2023-10-29T13:34:45 <DBG> [INFLUXDB] HTTP Client finished
[0d00h01m51s] 2023-10-29T13:34:45 <DBG> [INFLUXDB] HTTP request was performed
[0d00h01m51s] 2023-10-29T13:34:45 <DBG> [INFLUXDB] HTTP status code204
[0d00h01m51s] 2023-10-29T13:34:45 <DBG> [INFLUXDB] HTTP Client Disconnected

Expected Behavior

No response

Screenshots

No response

Additional Context

No response

@Reinhard-M Reinhard-M added the bug Something isn't working label Oct 29, 2023
@nhet
Copy link

nhet commented Oct 31, 2023

Kann ich bestätigen.
Die Zeiten scheinen nicht ganz zu passen. Wir hängen aktuell 1h hinter UTC hinterher.
image
image

Im zweiten Bild kann man erkennen, dass weiterhin mit 2h Versatz in influx geschrieben wird. Der _time Wert hätte hier 10:24:00.000Z statt 09:24:00.000Z sein müssen.

@caco3 caco3 changed the title InfluyDB Timestamp InfluxDB Timestamp Oct 31, 2023
@caco3
Copy link
Collaborator

caco3 commented Oct 31, 2023

Die Lösung wäre da wohl, dass man immer UTC verwendet.

@Slider0007
Copy link
Collaborator

Slider0007 commented Oct 31, 2023

@Reinhard-M, @nhet:
I've prepared a PR which addresses the issue.
Would you please so kind and test the version + provide some feedback:
https://github.com/jomjol/AI-on-the-edge-device/actions/runs/6712200597 (This version is based on latest rolling branch.)

@jomjol, @caco3: FYI

@Reinhard-M
Copy link
Author

Hi Slider0007,
I've just tested, it's working fine. Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants