# Date field saved as default timezone **URL:** \ **Category:** Elasticsearch\ **Created:** [December 9, 2019, 2:48pm UTC](https://discuss.elastic.co/t/date-field-saved-as-default-timezone/211143 "2019-12-09T14:48:20Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [December 9, 2019, 2:48pm UTC](https://discuss.elastic.co/t/date-field-saved-as-default-timezone/211143/1 "2019-12-09T14:48:20Z")
I am back at this. I am seating in CST time zone. most all my source are in CST time zone but all my date field is saved in Elasticsearch as GMT time zone. and my kibana (default setup as ) browser timezone is converting that GMT back to CST why can't I save all my data at CST timezone and kibana takes it as is? problem I am not having is when I run sql query it give me data on different time format. it is getting confusing. ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [December 9, 2019, 6:51pm UTC](https://discuss.elastic.co/t/date-field-saved-as-default-timezone/211143/2 "2019-12-09T18:51:33Z")
This is output of my data from database DAY\_ACHIEVED records * * * **02-DEC-19 00 655400** but same thing is shows up in elastic is h | s ------------------------+--------------- 2019-12-02T00:00:00.000Z|635872.0 2019-12-02T01:00:00.000Z|128556.0 2019-12-02T02:00:00.000Z|116842.0 2019-12-02T03:00:00.000Z|126606.0 2019-12-02T04:00:00.000Z|114090.0 2019-12-02T05:00:00.000Z|127968.0 **2019-12-02T06:00:00.000Z|655400.0** at 6:00 but I want that to register at same time 02-Dec-19 00:00.00.000 ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [December 10, 2019, 12:45pm UTC](https://discuss.elastic.co/t/date-field-saved-as-default-timezone/211143/3 "2019-12-10T12:45:36Z")
All dates are stored in UTC (as milliseconds since the epoch, when using a `date` datatype). Kibana uses the browser timezone, you can change that, see [https://www.elastic.co/guide/en/kibana/current/advanced-options.html](https://www.elastic.co/guide/en/kibana/current/advanced-options.html) You can also change/configure timezones on queries/aggregations if needed. ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [December 10, 2019, 2:13pm UTC](https://discuss.elastic.co/t/date-field-saved-as-default-timezone/211143/4 "2019-12-10T14:13:06Z")
yes I understand I can change that. but we want to save data in CST. that way when you use sql it comes out correctly also if I can save data in CST then I can use brower as cst and it will display as it displays sames in database. if anyone runs cross check ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [December 10, 2019, 4:26pm UTC](https://discuss.elastic.co/t/date-field-saved-as-default-timezone/211143/5 "2019-12-10T16:26:39Z")
looks like something along this line. elk looks like have release this in 7.5 [https://www.elastic.co/blog/converting-local-time-to-iso-8601-time-in-elasticsearch?ultron=dec-2019&blade=newsletter&hulk=email&mkt\_tok=eyJpIjoiT1RkbE16ZzJOMlU1T1RnMSIsInQiOiJ4NmZySmFLS05xK1ZLd1dxQzZqbHRnSVRhb0YzWHg0VUJBMzB1NUpCZTFPdzN0ZXFTODhiOFFUdnQ0WTVYRUs1a0l5a2ZFanEzdDBtaU11dTRXNnB6N2txTUNzYlJHTTJadWloQit5SXZlN01TSFdZYVZqZUc4K2h6YWYrWjQrYSJ9](https://www.elastic.co/blog/converting-local-time-to-iso-8601-time-in-elasticsearch?ultron=dec-2019&blade=newsletter&hulk=email&mkt_tok=eyJpIjoiT1RkbE16ZzJOMlU1T1RnMSIsInQiOiJ4NmZySmFLS05xK1ZLd1dxQzZqbHRnSVRhb0YzWHg0VUJBMzB1NUpCZTFPdzN0ZXFTODhiOFFUdnQ0WTVYRUs1a0l5a2ZFanEzdDBtaU11dTRXNnB6N2txTUNzYlJHTTJadWloQit5SXZlN01TSFdZYVZqZUc4K2h6YWYrWjQrYSJ9) ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [December 11, 2019, 8:25am UTC](https://discuss.elastic.co/t/date-field-saved-as-default-timezone/211143/6 "2019-12-11T08:25:57Z")
I can only repeat what I said earlier: Dates are always stored in UTC. You can modify your queries or use an ingestion pipeline to get your data properly converted before indexing, like it is done in the link you mentioned. ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [December 11, 2019, 3:20pm UTC](https://discuss.elastic.co/t/date-field-saved-as-default-timezone/211143/7 "2019-12-11T15:20:01Z")
> [@spinscale](#): > > ed in UTC. You can modify your queries or use an ingestion pipeline to get your data properly converted Perefect thanks. I tested it. basically for CTS I have to use timezone =\> Etc/UTC and it will save my data in elasticsearch with same time and not will change to +6. then I will have to setup kibana (all user) timezone = Etc/UTC and they will see data on same time frame. for London data I don't have to worry because it is already in GMT and elasticsearch saves in GMT. ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [December 12, 2019, 8:48am UTC](https://discuss.elastic.co/t/date-field-saved-as-default-timezone/211143/8 "2019-12-12T08:48:50Z")
sounds good. quick reminder that there is daylight savings time in the UK, so make sure that is properly taken accounted for (or hopefully you can just ignore 🙂 ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [December 20, 2019, 4:23pm UTC](https://discuss.elastic.co/t/date-field-saved-as-default-timezone/211143/9 "2019-12-20T16:23:02Z")
back to this topic again if someone can help me I use timezone=\> Etc/UTC and it saves all my date as is in elasticsearch. I am sitting in CST timezone Now I want to do same to singapore. what would be equivalent for that? ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [December 20, 2019, 4:31pm UTC](https://discuss.elastic.co/t/date-field-saved-as-default-timezone/211143/10 "2019-12-20T16:31:10Z")
This date timezone is so confusing. what simply I want to do is save date field as is, the way it comes from source and tell kibana not to convert anything. is there a option for it? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 17, 2020, 4:31pm UTC](https://discuss.elastic.co/t/date-field-saved-as-default-timezone/211143/11 "2020-01-17T16:31:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.