support for default timezone in SigNoz UI

[prashant-shahi]

Is your feature request related to a problem?

Not at the moment. But it could potentially cause issues in the future.

There are a few threads related to timezone management:

1. Org/Tenant Level Timezone Management: The default timezone should be set based on the deployed location. An option to change the timezone should be available later in the organization settings.
2. User-Level Timezone Preference: Consider a scenario where the SigNoz cloud tenant is deployed in India for the organization ACME, and I am an editor for ACME accessing it from the UK. In this case, users might get confused without clear communication of this setup.

Describe the solution you'd like

• Introduce default timezone for the SigNoz project irrespective of the timezone of the user
• even support for specific timezone per user basis
• display the timezone context to users in time range selectors.

cc @ankitnayan

[riteshsp2000]

Hey @prashant-shahi @palashgdev I'd like to work on this issue.

Could you please elaborate a bit more on what exactly is expected outcome for this.

[palashgdev]

sure please go ahead

[srikanthccv]

Not at the moment. But it could potentially cause issues in the future.

Putting a default timezone will cause more issues than using the user's timezone. What potential problems does the browser time cause? Have you seen any application or project doing this?

[prashant-shahi]

Idea behind this was to have optional support for default timezone in SigNoz.

This would be desired and helpful in case of companies which are based on specific region, while the people involved might be distributed. Having a common time in SigNoz would be helpful to monitor specific downtime or performance issue by anyone in the team.

Default timezone feature in common in CMS, project management tools, database, and also in some of the web frameworks like Ruby on Rails and Django.

Note: The changes would be only from frontend side while data format in database layer as well as query-service would remain intact.

[riteshsp2000]

@prashant-shahi So in order to get this feature up, we would be wanting something like a dropdown or equivalent input in the settings panel from where the user can select what timezone they want and depending upon the selection, it would reflect throughout the project.

[RakshitFK1703]

Hi @riteshsp2000 @pranay01 @palashgdev Are there any updates on this feature request? It is a typical use case for log analysis and a common requirement for many users. Would it be possible to prioritise this?

[nitin302]

Any further update on this please?

[xahhy]

We also encounter this timezone issue in our production environment. Our logs also log the current timestamp in UTC timezone but when search it on SigNoz UI it used our local timezone which brings inconsistency and unnecessary extra effort for us to use it. It's better to have a dropdown in the log search UI to let us select whether we want to search based on local timezone or UTC like how AWS generally did.

[sharpshooter90]

@nityanandagohain, sharing a related timezone issue here. I have outlined a few points in detail: https://github.com/SigNoz/engineering-pod/issues/1754.

[prashant-shahi]

@sharpshooter90 Have updated PR description to include the shared points.

[GeekBoySupreme]

PS - All the point mentioned above had already been designed for earlier.

The timepicker had an iteration where we show them their active timezone. Find the Figma here

The user setting up the workspace gets an option to set a workspace timezone (which is default selected to the timezone of where the tenant is deployed). Find the Figma here

Timezone mention in workspace settings. Find the Figma here

We should ideally not need to worry about user timezone, and let the browser handled that based on the computer's timezone. Hence adding a toggle like this should be enough - Figma