# Field \[@timestamp\] of type \[keyword\] does not support custom time zones

**URL:** <https://discuss.elastic.co/t/field-timestamp-of-type-keyword-does-not-support-custom-time-zones/134231>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [June 1, 2018, 1:19pm UTC](https://discuss.elastic.co/t/field-timestamp-of-type-keyword-does-not-support-custom-time-zones/134231 "2018-06-01T13:19:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nuwancs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nuwancs/32/46419_2.png) [@nuwancs](https://discuss.elastic.co/u/nuwancs)\
**Post date:** [June 1, 2018, 1:19pm UTC](https://discuss.elastic.co/t/field-timestamp-of-type-keyword-does-not-support-custom-time-zones/134231/1 "2018-06-01T13:19:15Z")

</div>

Once I set packetbeat to use fields.yml I get following exception in elastic logs and on kibana dashboard.

Caused by: java.lang.IllegalArgumentException: Field [@timestamp] of type [keyword] does not support custom time zones

How can I fix this?

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [June 5, 2018, 1:43pm UTC](https://discuss.elastic.co/t/field-timestamp-of-type-keyword-does-not-support-custom-time-zones/134231/2 "2018-06-05T13:43:47Z")

</div>

> [@nuwancs](#):
>
> Once I set packetbeat to use fields.yml

That's the default behavior when using the ES output. Can you please elaborate on what you changed? The error you are reporting most likely means that there's a problem with your index template (either one is not installed or it has the wrong type for `@timestamp`).

You can check if the index template is installed by requesting `GET _template/filebeat*` from ES and checking that the template for your Filebeat version is installed and that it has an `index_patterns` field that match your index naming strategy.

You can also check how `@timestamp` is mapped for a particular index with `GET filebeat-*/_mapping/field/@timestamp`.

---

<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, 2018, 1:43pm UTC](https://discuss.elastic.co/t/field-timestamp-of-type-keyword-does-not-support-custom-time-zones/134231/3 "2018-07-03T13:43:53Z")

</div>

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