# The datetime zone id is not recognised for pattern 'yyyy-MM-dd HH:mm:ss'

**URL:** <https://discuss.elastic.co/t/the-datetime-zone-id-is-not-recognised-for-pattern-yyyy-mm-dd-hh-mm-ss/46846>\
**Category:** Logstash\
**Created:** [April 8, 2016, 8:44pm UTC](https://discuss.elastic.co/t/the-datetime-zone-id-is-not-recognised-for-pattern-yyyy-mm-dd-hh-mm-ss/46846 "2016-04-08T20:44:48Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![yahoo](https://avatars.discourse-cdn.com/v4/letter/y/898d66/32.png) [@yahoo](https://discuss.elastic.co/u/yahoo)\
**Post date:** [April 8, 2016, 8:44pm UTC](https://discuss.elastic.co/t/the-datetime-zone-id-is-not-recognised-for-pattern-yyyy-mm-dd-hh-mm-ss/46846/1 "2016-04-08T20:44:48Z")

</div>

Hi

I wanted to have one place for setting the time zone.

This code is working:

```
    date {
       match => ["file_time", "yyyy-MM-dd HH:mm:ss"]
       target => "@timestamp"
        timezone => "America/New_York"
    }

```

Then I changed it to

```
    mutate {
        add_field => ["mytimezone", "America/New_York"]
        }

    date {
       match => ["file_time", "yyyy-MM-dd HH:mm:ss"]
       target => "@timestamp"
       timezone => "%{mytimezone}"
       }

```

I got "Configuration OK" with --configtest.

But I get an error:  
Error: Cannot register filter date plugin. The error reported is:  
The datetime zone id '%{mytimezone}' is not recognised for pattern 'yyyy-MM-dd HH:mm:ss'  
You may be interested in the '--configtest' flag which you can

---

<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:** [June 15, 2016, 5:25pm UTC](https://discuss.elastic.co/t/the-datetime-zone-id-is-not-recognised-for-pattern-yyyy-mm-dd-hh-mm-ss/46846/2 "2016-06-15T17:25:31Z")

</div>

I suspect your date filter is too old. Support for %{field} references in the timezone option was added fairly recently.

---

<div class="post-metadata">

**Author:** ![yahoo](https://avatars.discourse-cdn.com/v4/letter/y/898d66/32.png) [@yahoo](https://discuss.elastic.co/u/yahoo)\
**Post date:** [August 14, 2016, 5:52pm UTC](https://discuss.elastic.co/t/the-datetime-zone-id-is-not-recognised-for-pattern-yyyy-mm-dd-hh-mm-ss/46846/3 "2016-08-14T17:52:01Z")

</div>

Hi  
I upgraded to Logstash 2.3.3 and still it did not work. I got wrong results.

---

<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:** [August 14, 2016, 6:31pm UTC](https://discuss.elastic.co/t/the-datetime-zone-id-is-not-recognised-for-pattern-yyyy-mm-dd-hh-mm-ss/46846/4 "2016-08-14T18:31:47Z")

</div>

If you're more specific I'll try to help. Do you get the same error message or what's happening?

---

<div class="post-metadata">

**Author:** ![azhukov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azhukov/32/15856_2.png) [@azhukov](https://discuss.elastic.co/u/azhukov)\
**Post date:** [May 12, 2017, 7:42am UTC](https://discuss.elastic.co/t/the-datetime-zone-id-is-not-recognised-for-pattern-yyyy-mm-dd-hh-mm-ss/46846/5 "2017-05-12T07:42:04Z")

</div>

hello, I have the same issue with Logstash 5.3.0

logstash@f866296b6901:~/bin$ logstash --version  
logstash 5.3.0

$ logstash-plugin list --verbose logstash-filter-date  
logstash-filter-date (3.1.3)

logstash.conf is pretty simple

```
    filter {
    	date {
    		match => ["[@metadata][timestamp]" , "ISO8601" ]
    		timezone => "%{mytz}"
    	}
     }

```

When I star LS I receive:

[ERROR][logstash.agent] Cannot load an invalid configuration {:reason=\>"The datetime zone id '%{mytz}' is not recognised"}

It's strange that there was a PR for that [https://github.com/logstash-plugins/logstash-filter-date/pull/31](https://github.com/logstash-plugins/logstash-filter-date/pull/31)

--

It's a bug [https://github.com/logstash-plugins/logstash-filter-date/issues/97](https://github.com/logstash-plugins/logstash-filter-date/issues/97)

---

<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:** [May 17, 2017, 1:43pm UTC](https://discuss.elastic.co/t/the-datetime-zone-id-is-not-recognised-for-pattern-yyyy-mm-dd-hh-mm-ss/46846/6 "2017-05-17T13:43:21Z")

</div>

@azhukov  
after PR 31 the date filter had a rewrite to add more Java and less ruby.  
tz interpolation does not work when `ISO8601` is specified - it should work for patterns though.

I am fixing the date filter as we speak.

---

<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:** [May 17, 2017, 1:45pm UTC](https://discuss.elastic.co/t/the-datetime-zone-id-is-not-recognised-for-pattern-yyyy-mm-dd-hh-mm-ss/46846/7 "2017-05-17T13:45:57Z")

</div>

version 2.3.4 has a version of the date filter that supports tz interpolation

---

<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, 4:26am UTC](https://discuss.elastic.co/t/the-datetime-zone-id-is-not-recognised-for-pattern-yyyy-mm-dd-hh-mm-ss/46846/8 "2017-07-06T04:26:31Z")

</div>