# Today date data is coming into previous index

**URL:** <https://discuss.elastic.co/t/today-date-data-is-coming-into-previous-index/360312>\
**Category:** Elasticsearch\
**Created:** [May 27, 2024, 3:48pm UTC](https://discuss.elastic.co/t/today-date-data-is-coming-into-previous-index/360312 "2024-05-27T15:48:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aniket\_Pant](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@Aniket\_Pant](https://discuss.elastic.co/u/Aniket_Pant)\
**Post date:** [May 27, 2024, 3:48pm UTC](https://discuss.elastic.co/t/today-date-data-is-coming-into-previous-index/360312/1 "2024-05-27T15:48:20Z")

</div>

Hi Community,

We have DC-DR(Active Active)ELK cluster running. We have Observed that for 2024-05-25 00:00-23:59 time range in discover if i select \_index i am seeing index-2024-05-27. For Replication from DC to DR we are using Kafka mirror. This issue is happening in DR.

---

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [May 28, 2024, 9:27am UTC](https://discuss.elastic.co/t/today-date-data-is-coming-into-previous-index/360312/2 "2024-05-28T09:27:24Z")

</div>

Hi @Aniket_Pant,

Do you have ILM setup to rollover your indices? If so can you share your policy please?

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [May 28, 2024, 12:26pm UTC](https://discuss.elastic.co/t/today-date-data-is-coming-into-previous-index/360312/3 "2024-05-28T12:26:02Z")

</div>

> [@Aniket\_Pant](#):
>
> We have Observed that for 2024-05-25 00:00-23:59 time range in discover if i select \_index i am seeing index-2024-05-27.

You need to provide a lot more of context, for example, how are you indexing your data? Are you using logstash?

It is not possible to know what the issue may be or even if this is an issue without more information.

But if you are using logstash and you are not using the date string from your log messages, logstash will use the timestamp from when the log has entered the pipeline.

This is also the behaviour of any other tool, if you do not specifiy it to use a date field from your message, it will use the current date as the value for the `@timestamp` field.