# Date filter: Text Time zone names (z) cannot be parsed

**URL:** <https://discuss.elastic.co/t/date-filter-text-time-zone-names-z-cannot-be-parsed/88304>\
**Category:** Logstash\
**Created:** [June 5, 2017, 5:00pm UTC](https://discuss.elastic.co/t/date-filter-text-time-zone-names-z-cannot-be-parsed/88304 "2017-06-05T17:00:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![oraclept](https://avatars.discourse-cdn.com/v4/letter/o/ce73a5/32.png) [@oraclept](https://discuss.elastic.co/u/oraclept)\
**Post date:** [June 5, 2017, 5:00pm UTC](https://discuss.elastic.co/t/date-filter-text-time-zone-names-z-cannot-be-parsed/88304/1 "2017-06-05T17:00:51Z")

</div>

Hi - I am having

a. May 30, 2017 10:13:48 PM EST date and time format.

b. grokking with (?\s?%{MONTH}\s+%{MONTHDAY},\s+%{YEAR}\s?%{HOUR}:%{MINUTE}:%{SECOND}\s+[[Aa]|[Pp]][Mm]?\s+%{TZ}) - Grok works perfect.

c. using date filter to store @timestamp with mylocaltimestamp.

using date filter I get \_dateparsefailure error. How to deal with short timezones

Joda equivalent is : z time zone text Pacific Standard Time; PST  
Date filter: z time zone names. Time zone names (z) cannot be parsed.

```
`date {
      		  match => ["mylocaltimestamp", "MMM dd, YYYY hh:mm:ss a Z"]
         timezone => "America/New_York"
         target => "@timestamp"
     }`

```

--ouput

```
{
            "path" => "C:\\Users\\d452\\Downloads\\ELK\\input\\logstash-Input.txt",
      "@timestamp" => 2017-06-05T15:54:12.267Z,
"mylocaltimestamp" => "May 30, 2017 10:13:48 PM EDT",
        "@version" => "1",
            "host" => "LT-00008443",
         "message" => "May 30, 2017 10:13:48 PM EST\r",
            "type" => "localfile",
            "tags" => [
    [0] "_dateparsefailure"
]

```

}

How to address text timezone when it cannot be parsed with date filter.

Thanks for time,

---

<div class="post-metadata">

**Author:** ![oraclept](https://avatars.discourse-cdn.com/v4/letter/o/ce73a5/32.png) [@oraclept](https://discuss.elastic.co/u/oraclept)\
**Post date:** [June 5, 2017, 5:36pm UTC](https://discuss.elastic.co/t/date-filter-text-time-zone-names-z-cannot-be-parsed/88304/2 "2017-06-05T17:36:26Z")

</div>

Looking at the forum posts.

Below are options

1. use Translate Filter
2. Change log format.

> [@Logstash timestamp error when CEST is at the end](https://discuss.elastic.co/t/logstash-timestamp-error-when-cest-is-at-the-end/27843/2):
>
> Quoting the [Joda-Time documentation](http://joda-time.sourceforge.net/apidocs/org/joda/time/format/DateTimeFormat.html): Zone names: Time zone names ('z') cannot be parsed So, unless you can hardcode the timezone in the date filter configuration I think you need to translate the timezone names into offsets and include the offset in the timestamp to be parsed.

Thanks,

---

<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 3, 2017, 5:36pm UTC](https://discuss.elastic.co/t/date-filter-text-time-zone-names-z-cannot-be-parsed/88304/3 "2017-07-03T17:36:37Z")

</div>

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