# Logstash 2.2.2 date filter returning wrong day

**URL:** https://discuss.elastic.co/t/logstash-2-2-2-date-filter-returning-wrong-day/42957
**Category:** Logstash
**Created:** [February 28, 2016, 6:10pm UTC](https://discuss.elastic.co/t/logstash-2-2-2-date-filter-returning-wrong-day/42957 "2016-02-28T18:10:42Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Stuart\_Donovan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stuart_donovan/32/7808_2.png) [@Stuart\_Donovan](https://discuss.elastic.co/u/Stuart_Donovan)
#### Post date: [February 28, 2016, 6:10pm UTC](https://discuss.elastic.co/t/logstash-2-2-2-date-filter-returning-wrong-day/42957/1 "2016-02-28T18:10:42Z")

</div>

This works fine with logstash 1.5.6 but with logstash 2.2.2 it sets @timestamp to the previous day??

echo "Mon Feb 22 22:20:41.144" | /opt/logstash/bin/logstash -e '

> input { stdin {codec =\> line} }  
> filter { date { match =\> ["message" , "EEE MMM dd HH:mm:ss.SSS"] } }  
> output { stdout {codec =\> rubydebug} }  
> '  
> Settings: Default pipeline workers: 2  
> Logstash startup completed  
> {  
> "message" =\> "Mon Feb 22 22:20:41.144",  
> "@version" =\> "1",  
> "@timestamp" =\> "2016-02-21T22:20:41.144Z",  
> "host" =\> "0.0.0.0"  
> }  
> Logstash shutdown completed

Any ideas?

---

<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 28, 2016, 6:31pm UTC](https://discuss.elastic.co/t/logstash-2-2-2-date-filter-returning-wrong-day/42957/2 "2016-02-28T18:31:40Z")

</div>

That's odd. I can't reproduce. Which timezone are you in?

---

<div class="post-metadata">

### Author: ![Stuart\_Donovan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stuart_donovan/32/7808_2.png) [@Stuart\_Donovan](https://discuss.elastic.co/u/Stuart_Donovan)
#### Post date: [February 28, 2016, 6:57pm UTC](https://discuss.elastic.co/t/logstash-2-2-2-date-filter-returning-wrong-day/42957/3 "2016-02-28T18:57:24Z")

</div>

Arg ☹

I am testing on a canonical Ubuntu EC2 instance with just java and logstash installed:

$ java -version  
java version "1.8.0\_72"  
Java(TM) SE Runtime Environment (build 1.8.0\_72-b15)  
Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode)

$ /opt/logstash/bin/logstash -V  
logstash 2.2.2  
$ uname -a  
Linux ip-10-0-4-211 3.13.0-74-generic #118-Ubuntu SMP Thu Dec 17 22:52:10 UTC 2015 x86\_64 x86\_64 x86\_64 GNU/Linux  
$ date +'%:z %Z'  
+00:00 UTC

---

<div class="post-metadata">

### Author: ![Stuart\_Donovan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stuart_donovan/32/7808_2.png) [@Stuart\_Donovan](https://discuss.elastic.co/u/Stuart_Donovan)
#### Post date: [February 28, 2016, 7:01pm UTC](https://discuss.elastic.co/t/logstash-2-2-2-date-filter-returning-wrong-day/42957/4 "2016-02-28T19:01:17Z")

</div>

Also if I insert the year in front it works fine:  
echo "2016 Mon Feb 22 22:20:41.999" | /opt/logstash/bin/logstash -e '  
input { stdin {codec =\> line} }  
filter { date { match =\> ["message" , "YYYY EEE MMM dd HH:mm:ss.SSS"] } }  
output { stdout {codec =\> rubydebug} }  
'  
Settings: Default pipeline workers: 2  
Logstash startup completed  
{  
"message" =\> "2016 Mon Feb 22 22:20:41.999",  
"@version" =\> "1",  
"@timestamp" =\> "2016-02-22T22:20:41.999Z",  
"host" =\> "0.0.0.0"  
}  
Logstash shutdown completed

---

<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 6, 2017, 5:09am UTC](https://discuss.elastic.co/t/logstash-2-2-2-date-filter-returning-wrong-day/42957/5 "2017-07-06T05:09:28Z")

</div>


