Hello All, I am experiencing an issue where the raw “timestamp” field stored in Elasticsearch is formatted as below: “timestamp”:“2022-01-20 16:38:50.438” As you can see, this timestamp does not include any time zone information. The time zone actually used is UTC. According to ISO 8601/RFC 333…

Hello, [image] c0herent: Is this behavior something that can be fixed in a patch? You could post here if you believe this is a bug or feature request. [image] Build software better, together GitHub is where people build software. More than 100 million people use GitHub to discov…

Hi @gsmith , Thanks for the info. I will try that workaround if I run into a message that only has the default timestamp. I will also investigate whether it makes sense to file this as a bug report. Thanks! -Ben

Submitted bug #12104 for this: Default “timestamp” field does not contain time zone information opened 03:32PM - 08 Feb 22 UTC (UTC) [c0herent] c0herent …

Nice :+1: Thanks for keeping us informed :slight_smile:

Default "timestamp" field does not contain time zone information

Graylog Central (peer support)

Topic		Replies	Views
Timezone best practice (Grafana issues) Graylog Central (peer support)	2	1249	February 2, 2020
Graylog messages were showing two different timestamp values Graylog Central (peer support)	1	881	June 28, 2018
Timezone issues. Logs are shown 1 hour behind Graylog Central (peer support)	7	3580	September 3, 2020
The timestamp returned by the graylog API is abnormal Graylog Central (peer support) timestamp	9	487	March 24, 2023
@timestamp field format in Graylog GUI Search doesn't show as UTC ISO8601 sent by filebeat beat Graylog Central (peer support) filebeat-linux , timestamp	8	1418	April 29, 2023

Default "timestamp" field does not contain time zone information

Related topics