# Elastalert: Problem with @timestamp field **URL:** \ **Category:** Elasticsearch\ **Created:** [October 3, 2018, 6:49am UTC](https://discuss.elastic.co/t/elastalert-problem-with-timestamp-field/150830 "2018-10-03T06:49:18Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![ashwinid](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@ashwinid](https://discuss.elastic.co/u/ashwinid)\ **Post date:** [October 3, 2018, 6:49am UTC](https://discuss.elastic.co/t/elastalert-problem-with-timestamp-field/150830/1 "2018-10-03T06:49:19Z")
I am installing elastalert (version :0.1.33) on the linux (7.5) server where my elasticsearch(6.4) is also installed. I am not able to send the alert messages at the real time. My timezone is UTC+5.30 and elastalert send the alert messages with the timezone UTC 0. Please provide the solution. ---
**Author:** ![martijnrondeel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/martijnrondeel/32/35415_2.png) [@martijnrondeel](https://discuss.elastic.co/u/martijnrondeel)\ **Post date:** [October 4, 2018, 8:47am UTC](https://discuss.elastic.co/t/elastalert-problem-with-timestamp-field/150830/2 "2018-10-04T08:47:58Z")
Are you using Docker to run it? If so, please try our latest version where the [timezone issue](https://github.com/bitsensor/elastalert/issues/33) should be fixed. (Also if you have problems with ElastAlert in the future please open an issue [here](https://github.com/bitsensor/elastalert/issues). This forum is not really the right place for ElastAlert support.) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 1, 2018, 8:48am UTC](https://discuss.elastic.co/t/elastalert-problem-with-timestamp-field/150830/3 "2018-11-01T08:48:04Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.