# Changing the date Filter to get exact same timestamp in kibana as in log

**URL:** <https://discuss.elastic.co/t/changing-the-date-filter-to-get-exact-same-timestamp-in-kibana-as-in-log/76009>\
**Category:** Logstash\
**Created:** [February 22, 2017, 9:54am UTC](https://discuss.elastic.co/t/changing-the-date-filter-to-get-exact-same-timestamp-in-kibana-as-in-log/76009 "2017-02-22T09:54:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![anisen](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@anisen](https://discuss.elastic.co/u/anisen)\
**Post date:** [February 22, 2017, 9:54am UTC](https://discuss.elastic.co/t/changing-the-date-filter-to-get-exact-same-timestamp-in-kibana-as-in-log/76009/1 "2017-02-22T09:54:29Z")

</div>

Hi, My log looks like below:

[www.xyz.com](http://www.xyz.com) 100.181.12.41 - - [04/Dec/2013:07:35:39 -0600] "GET /abc/images/someimage.png HTTP/1.1" 200

My Grok filter is as below:

grok {  
match =\> {  
"message" =\> '%{NOTSPACE:domainname} %{IPORHOST:clientip} %{NOTSPACE:username} %{NOTSPACE:auth} [%{HTTPDATE:timestamp}] "%{NOTSPACE:method} %{NOTSPACE:uri} HTTP/%{NOTSPACE:httpversion}" %{NOTSPACE:status}'  
}  
}

And Date filter:

date {  
match =\> ["timestamp", "dd/MMM/YYYY:HH:mm:ss Z"]  
timezone =\> "America/Chicago"  
}

But, after processing the record, in Kibana the @timestamp is "December 4th 2013, 19:05:43.000"

I want it to be "December 4th 2013, 07:35:39.000" . What changes do I need to make? Please suggest.

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [February 22, 2017, 12:17pm UTC](https://discuss.elastic.co/t/changing-the-date-filter-to-get-exact-same-timestamp-in-kibana-as-in-log/76009/2 "2017-02-22T12:17:04Z")

</div>

Is the actual timestamp in `@timestamp` correct and in UTC? What's the timezone of the computer where your browser runs?

---

<div class="post-metadata">

**Author:** ![anisen](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@anisen](https://discuss.elastic.co/u/anisen)\
**Post date:** [February 22, 2017, 1:19pm UTC](https://discuss.elastic.co/t/changing-the-date-filter-to-get-exact-same-timestamp-in-kibana-as-in-log/76009/3 "2017-02-22T13:19:57Z")

</div>

Hi, Thanks for the response.

In Kibana @timestamp was not coming correctly. And, the browser's timezone is +0530 .

But, with the below date filter I got the desired result:

date{  
match =\> ["timestamp", "dd/MMM/YYYY:HH:mm:ss -0600"]  
}

Is this the correct way to do this?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [February 22, 2017, 1:25pm UTC](https://discuss.elastic.co/t/changing-the-date-filter-to-get-exact-same-timestamp-in-kibana-as-in-log/76009/4 "2017-02-22T13:25:14Z")

</div>

By default Kibana adjusts the UTC timestamps stored in ES to the browser's timezone. If you don't want that the proper solution is to change Kibana's configuration (Settings -\> Advanced, at least in Kibana 4) to use a specific timezone (UTC-6 in this case). Do not attempt to work around the problem by storing anything but UTC in Elasticsearch.

---

<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:** [March 22, 2017, 1:25pm UTC](https://discuss.elastic.co/t/changing-the-date-filter-to-get-exact-same-timestamp-in-kibana-as-in-log/76009/5 "2017-03-22T13:25:23Z")

</div>

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