# @timestamp for time zone issues

**URL:** https://discuss.elastic.co/t/timestamp-for-time-zone-issues/275507
**Category:** Logstash
**Created:** [June 9, 2021, 11:11pm UTC](https://discuss.elastic.co/t/timestamp-for-time-zone-issues/275507 "2021-06-09T23:11:32Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![asasas234](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asasas234/32/113152_2.png) [@asasas234](https://discuss.elastic.co/u/asasas234)
#### Post date: [June 9, 2021, 11:11pm UTC](https://discuss.elastic.co/t/timestamp-for-time-zone-issues/275507/1 "2021-06-09T23:11:32Z")

</div>

I have an old logstash docker image, its version is 6.2.2 and the time zone is +0800, my new logstash docker image version is 7.12.1 , the time zone is +0000, but there is a surprising result, the final output @timestamp value of the 6.2.2 version is +0000, while the 7.12.1 output @timestamp value is +0800, I do not understand why this is so? Here is my relevant logstash configuration

```auto
grok{
        match => {"message" => "\[%{TIMESTAMP_ISO8601:log_time}\] \[%{LOGLEVEL:level}\] \[%{DATA:thread}\] %{GREEDYDATA:class_name} %{NUMBER:line_num} \[%{GREEDYDATA:trace_id}\] - %{GREEDYDATA:content}"}
    }

date {
        match => ["log_time", "yyyy-MM-dd HH:mm:ss.SSS"]
    }

```

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 7, 2021, 11:12pm UTC](https://discuss.elastic.co/t/timestamp-for-time-zone-issues/275507/2 "2021-07-07T23:12:06Z")

</div>

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