# Change in Time In elasticsearch and Database
**URL:** https://discuss.elastic.co/t/change-in-time-in-elasticsearch-and-database/338869
**Category:** Elasticsearch
**Tags:** kql-kibana-query-language
**Created:** [July 20, 2023, 9:57am UTC](https://discuss.elastic.co/t/change-in-time-in-elasticsearch-and-database/338869 "2023-07-20T09:57:52Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@UshasMerrinGeorge](https://discuss.elastic.co/u/UshasMerrinGeorge)
#### Post date: [July 20, 2023, 9:57am UTC](https://discuss.elastic.co/t/change-in-time-in-elasticsearch-and-database/338869/1 "2023-07-20T09:57:52Z")
Hi all,
I'm having trouble with data parsing from a database to Elasticsearch.
The "downloaddate" field in the database has a value like "2023-07-12 17:30:17.000."
When I print it in the terminal using stdout, it's correct.
However, when indexed in Elasticsearch, the time changes to (Jul 12, 2023 @ 23:00:17.000).
I tried using a date filter, but the issue remains unresolved.
I'd appreciate any suggestions or help in resolving this time difference problem.
Thank you!
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [July 20, 2023, 10:08am UTC](https://discuss.elastic.co/t/change-in-time-in-elasticsearch-and-database/338869/2 "2023-07-20T10:08:32Z")
All timestamps in Elasticsearch are in UTC timezone. Kibana do translate the default timestamp to the local timezone when displaying it, which likely is what you are seeing.
---
### Author:  [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)
#### Post date: [July 20, 2023, 12:43pm UTC](https://discuss.elastic.co/t/change-in-time-in-elasticsearch-and-database/338869/3 "2023-07-20T12:43:51Z")
> [@UshasMerrinGeorge](#):
>
> I tried using a date filter, but the issue remains unresolved.
>
> I'd appreciate any suggestions or help in resolving this time difference problem.
As already mentioned all dates in Elasticsearch are stored in UTC and Kibana will convert this UTC date to your local timezone.
The issue here is that your date string does not have any information about the timezone, so Logstash will consider that this date is already in UTC, this is what you get in your stdout output.
The **Z** in the end of the date means that it is in UTC.
If your date `2023-07-12 17:30:17.000` **is not** in UTC, but in your local time zone, you need to inform this to logstash in the date filter using the `timezone` option.
Since Kibana is showing 17:30:17 UTC as 23:00:17 in your local timezone, you are in a UTC+5:30 timezone, so you need to inform that to Logstash.
You can do that adding the canonical name of your timezone, something like `Asia/Kolkata` which is UTC+5:30, or you can use the numerical offset directly as `+0530`, but the canonical name is recommended as it will also applies DST changes if it exists.
Use the canonical name or the numeric offset, do not use the abbreviated timezone names like `IST` as this can not work as expected.
---
### Author:  [@UshasMerrinGeorge](https://discuss.elastic.co/u/UshasMerrinGeorge)
#### Post date: [July 21, 2023, 8:01am UTC](https://discuss.elastic.co/t/change-in-time-in-elasticsearch-and-database/338869/4 "2023-07-21T08:01:04Z")
When I parse the data to my local Elasticsearch instance, there is no difference in time. However, when I parse it to Elasticsearch in azure VM, that time difference occurs.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 18, 2023, 8:01am UTC](https://discuss.elastic.co/t/change-in-time-in-elasticsearch-and-database/338869/5 "2023-08-18T08:01:51Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.