Timezone issue

In our current kibana setup , the timezone has been set to browser timezone. This dashboard is live for users in India as well as users in Ireland . The kibana setup is live and linked to spinnaker to monitor the pipelines. But we are facing an issue and difference with the data being displayed for users in India and users in Ireland. Here we are able to get valid data with kibana and spinnaker set to local timezone for us. Could you please suggest any possible way we could take up to have a standard timezone for all the users across all the locations in Kibana.

You can fix it in stack management > advanced settings (by default it's taking the browser default):

Hi @flash1293 ,
Currently in our kibana dashboard the timezone is set to browser . Whereas we are seeing difference in data for users in India and users in Ireland. Any idea how we can have a standard timezone so the data is uniform for both the users.

What is the difference you are seeing? Can you provide more context and examples?

How are you ingesting your data? Does your date string have timezone information?

All data in Elasticsearch is stored as UTC, if you send a date string to Elasticsearch without specifying the timezone offset, it will assume that the date is in UTC.

For example, if you have something like this:

  • 2022-11-10 09:30:00 (local time Ireland)
  • 2022-11-10 09:30:00 (local time India)

They both will be treated as being in UTC by elasticsearch, which is wrong for India, since it is not in UTC, but it is correct for Ireland since it is in GMT time, which is the same as UTC.

The correct time would be:

  • 2022-11-10 04:00:00 (local time Ireland)
  • 2022-11-10 09:30:00 (local time India)

Since India is 05:30 ahead of UTC.

Can you provide more context on how your date string looks like in both locations and how are you ingesting your data?

See my post above - if you set it to a specific time zone there, then all users of Kibana will use the configured time zone, no matter their browser configuration.

Hi @leandrojmp ,

image

This is how we are feeding data to kibana through script but we have not given any timezone in the script.

The timezone in my kibana setup is set to Browser by default.

So you suggest we change the above timezone setting from BROWSER to UTC to fix the difference in data we are seeing in India and Ireland

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.

Hi @leandrojmp ,
Currently in our script we are using this
image

As I said in the previous answer.

You need to convert your date string to UTC, how you will do that depends on your script language and your code.

Also, you still didn't say what is the difference you are seeing and didn't provide any example of your issue, so it is not possible to know if this would fix it.

Hi @leandrojmp ,

There is graph for the pipeline pass and fail rate , data coming from the spinnaker .
Both are correct according to two country's time zone.


left side graph is represent the ireland pipeline data,right side one represents the india pipeline data
The kibana setup is live and linked to spinnaker to monitor the pipelines. But we are facing an issue and difference with the data being displayed for users in India and users in Ireland

And What is the issue? It is not clear, you need to share examples of this issue, share example of your data, and what is wrong, do not share screenshots as they do not help to understand, you need to share example of messages that are not working as expected.

Check my previous answer.

What are the date strings of your data in both of those locations? It is still not clear what is this difference you are telling and what is the issue.