# Date Filter Woes

**URL:** <https://discuss.elastic.co/t/date-filter-woes/192737>\
**Category:** Logstash\
**Created:** [July 29, 2019, 3:21pm UTC](https://discuss.elastic.co/t/date-filter-woes/192737 "2019-07-29T15:21:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![wwalker](https://avatars.discourse-cdn.com/v4/letter/w/43a26b/32.png) [@wwalker](https://discuss.elastic.co/u/wwalker)\
**Post date:** [July 29, 2019, 3:21pm UTC](https://discuss.elastic.co/t/date-filter-woes/192737/1 "2019-07-29T15:21:48Z")

</div>

I have a field that tracks when a ticket was created, `sys_created_on`. The time is in local timezone, -05:00 currently. I have the following logstash config:

```auto
  date {
    match => ["sys_created_on", "yyyy-MM-dd HH:mm:ss"]
    timezone => "America/Chicago"
  }

```

In Kibana, I am using the `@timestamp` field as the time field. When events come up in Kibana, they show a time that is five hours in the future. When I look at the JSON data, it is showing a timestamp 10 hours in the future. What the hell am I doing wrong??

---

<div class="post-metadata">

**Author:** ![guyboertje](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guyboertje/32/31592_2.png) [@guyboertje](https://discuss.elastic.co/u/guyboertje)\
**Post date:** [July 30, 2019, 4:40pm UTC](https://discuss.elastic.co/t/date-filter-woes/192737/2 "2019-07-30T16:40:21Z")

</div>

What timezone is the logstash server running in?

It should be UTC. Try setting `TZ=UTC` as a shell variable before invoking LS.

e.g. `TZ=UTC bin/logstash -f ...`

---

<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:** [August 27, 2019, 4:40pm UTC](https://discuss.elastic.co/t/date-filter-woes/192737/3 "2019-08-27T16:40:26Z")

</div>

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