# Dynamically assigning timezone from a filebeat event
**URL:** https://discuss.elastic.co/t/dynamically-assigning-timezone-from-a-filebeat-event/125669
**Category:** Logstash
**Created:** [March 26, 2018, 7:33pm UTC](https://discuss.elastic.co/t/dynamically-assigning-timezone-from-a-filebeat-event/125669 "2018-03-26T19:33:37Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@rajisankar](https://discuss.elastic.co/u/rajisankar)
#### Post date: [March 26, 2018, 7:33pm UTC](https://discuss.elastic.co/t/dynamically-assigning-timezone-from-a-filebeat-event/125669/1 "2018-03-26T19:33:37Z")
I am shipping logs to logstash from filebeat. I have added the processor to add beat.timezone. But, when beat.timezone returns "EDT" (which currently is correct), logstash fails to parse as its unable to identify EDT. in Joda timezone, EDT is referred as EST5EDT. Is there a way to overcome this issue in logstash and parse timezones from filebeat?
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [March 26, 2018, 7:47pm UTC](https://discuss.elastic.co/t/dynamically-assigning-timezone-from-a-filebeat-event/125669/2 "2018-03-26T19:47:21Z")
You could use a translate filter in Logstash to translate EDT values to EST4EDT (or a UTC offset). Sure, you'll have to enumerate all timezone values you'll be using but presumably they're not too many of them.
---
### Author:  [@rajisankar](https://discuss.elastic.co/u/rajisankar)
#### Post date: [March 26, 2018, 7:59pm UTC](https://discuss.elastic.co/t/dynamically-assigning-timezone-from-a-filebeat-event/125669/3 "2018-03-26T19:59:53Z")
Thought about it,but yeah, need to add for all the relevant timezones. Was hoping for a more straightforward solution as EDT is part of ISO.
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [March 27, 2018, 6:46am UTC](https://discuss.elastic.co/t/dynamically-assigning-timezone-from-a-filebeat-event/125669/4 "2018-03-27T06:46:47Z")
What ISO standard describes EDT?
---
### Author:  [@rajisankar](https://discuss.elastic.co/u/rajisankar)
#### Post date: [March 27, 2018, 7:03pm UTC](https://discuss.elastic.co/t/dynamically-assigning-timezone-from-a-filebeat-event/125669/5 "2018-03-27T19:03:52Z")
My bad. I meant that EDT is an accepted standard timezone specification.
From [https://www.cl.cam.ac.uk/~mgk25/iso-time.html](https://www.cl.cam.ac.uk/~mgk25/iso-time.html) ,
"There exists no international standard that specifies abbreviations for civil time zones like CET, EST, etc. and sometimes the same abbreviation is even used for two very different time zones. In addition, politicians enjoy modifying the rules for civil time zones, especially for daylight saving times, every few years, so the only really reliable way of describing a local time zone is to specify numerically the difference of local time to UTC. Better use directly UTC as your only time zone where this is possible and then you do not have to worry about time zones and daylight saving time changes at all."
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 24, 2018, 7:04pm UTC](https://discuss.elastic.co/t/dynamically-assigning-timezone-from-a-filebeat-event/125669/6 "2018-04-24T19:04:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.