No, this will not fix your issue and will complicated even more for your Kibana users in India as they will need to work on a different timezone and make calculations to find the correct time.
To fix your issue you need to inform elasticsearch that your date strings are in local time, you need to inform what is the timezone offset of the date strings.
As I said in the previous answer, Elasticsearch store dates in UTC and Kibana will convert this UTC time to the local time.
The main issue here is that you are use ingesting data in local time in a place that has an timezone offset.
If you have an event that happened at 2022-11-11 09:30:00 in India local time, and ingest this date string without telling Elastiscearch that this time has an offset from UTC, it will be ingested as happening at 2022-11-11 09:30:00Z, which is 09:30 UTC.
Kibana will them convert this UTC time to your India local time, which would be the equivalent of 2022-11-11 15:00:00 local.
To tix this, you need to ingest the 2022-11-11 09:30:00 date string telling Elasticsearch that this has an offset, so you would use something like 2022-11-11 09:30:00 +05:30, this date will then be stored as UTC as 2022-11-11 04:00:00Z and your users in India will se this date in their local time.
In resume, you will have this:
- UTC time of event:
2022-11-11 04:00:00Z - Local time when the users in Ireland will see the event:
2022-11-11 04:00:00 - Local time when the users in India will see the event:
2022-11-11 09:30:00
You need to change your script to format the date string to be in UTC and have the offset of the timezone.