# Problem with timezone conversion - full timestamp vs time only

**URL:** <https://discuss.elastic.co/t/problem-with-timezone-conversion-full-timestamp-vs-time-only/140817>\
**Category:** Kibana\
**Created:** [July 19, 2018, 11:55pm UTC](https://discuss.elastic.co/t/problem-with-timezone-conversion-full-timestamp-vs-time-only/140817 "2018-07-19T23:55:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cvraocv](https://avatars.discourse-cdn.com/v4/letter/c/3e96dc/32.png) [@cvraocv](https://discuss.elastic.co/u/cvraocv)\
**Post date:** [July 19, 2018, 11:55pm UTC](https://discuss.elastic.co/t/problem-with-timezone-conversion-full-timestamp-vs-time-only/140817/1 "2018-07-19T23:55:03Z")

</div>

All,

I am facing a problem with inconsitent timezone conversion in visualization - between a full timestamp field and a time only field. Looked around and didn't find a solution. Please help!

I have loaded 2 different date fields into Elastic like below in UTC. Using the console, I am able to see the same - correctly. FYI, actual time is just the time portion of end date. Loaded this data using logstash

```
"enddate": "2018-07-19 12:10:45",
"actualtime": "12:10:45",

```

![image](https://us1.discourse-cdn.com/elastic/original/3X/a/3/a3327aa67c5735595cec7941ae8bfefb73edeac7.png)

My browser / system is in Pacific time zone. With Day light savings on, we expect it to subtract 7 hours from the UTC data loaded above.

In Discover, I was able to see enddate correctly as **5:10: 45** in PDT, but looks like actual time is getting subtracted with 8 hours and not 7 - which is the case with PST and not PDT - showing **4:10:45**

enddate:July 19th 2018, 05:10:45.000 actualtime:04:10:45

![image](https://us1.discourse-cdn.com/elastic/original/3X/0/5/055db52b72de5efdca4a5142ba8d1e5038211d6e.png)

Both the fields are defined as Date fields in the mapping and I am using the pattern as "HH:mm:ss" for actual time

Let me know if there is anything I am missing here and thanks in advance for your help!

Regards,  
Venkat

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [July 27, 2018, 2:37pm UTC](https://discuss.elastic.co/t/problem-with-timezone-conversion-full-timestamp-vs-time-only/140817/2 "2018-07-27T14:37:34Z")

</div>

Hello,

This seems interesting but I think it's more on how Elasticsearch sees times without any date information assigned to it. By default, I remember that all times are saved as UTC, but what conversion happens there for you will be different: enddate takes it as the time on the date, with DST on, and for the time without any date assigned to it will most likely default to no DST. This will be why you see the difference. You can ask in the Elasticsearch forums to confirm this.

---

<div class="post-metadata">

**Author:** ![cvraocv](https://avatars.discourse-cdn.com/v4/letter/c/3e96dc/32.png) [@cvraocv](https://discuss.elastic.co/u/cvraocv)\
**Post date:** [July 27, 2018, 6:06pm UTC](https://discuss.elastic.co/t/problem-with-timezone-conversion-full-timestamp-vs-time-only/140817/3 "2018-07-27T18:06:43Z")

</div>

Thank you Marius for your reply. I will try in the ES forum

Regards,  
Venkat

---

<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:** [August 24, 2018, 6:06pm UTC](https://discuss.elastic.co/t/problem-with-timezone-conversion-full-timestamp-vs-time-only/140817/4 "2018-08-24T18:06:47Z")

</div>

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