SigNoz / signoz

SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool
https://signoz.io
Other
19.45k stars 1.31k forks source link

support for default timezone in SigNoz UI #2723

Open prashant-shahi opened 1 year ago

prashant-shahi commented 1 year ago

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

cc @ankitnayan

riteshsp2000 commented 1 year ago

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 commented 1 year ago

sure please go ahead

srikanthccv commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

@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 commented 6 months ago

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 commented 2 months ago

Any further update on this please?

xahhy commented 1 month ago

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 commented 1 month ago

@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 commented 1 month ago

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

GeekBoySupreme commented 1 month ago

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 image

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 image

Timezone mention in workspace settings. Find the Figma here

image

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 image

ankitnayan commented 2 weeks ago

https://github.com/SigNoz/engineering-pod/issues/1962

ankitnayan commented 2 weeks ago

what if SigNoz's tenant is in us-east-1, the customer's machine is in us-west-1 and the user is in eu-central-1

micahnz commented 1 week ago

I'd like to see global frontend setting and user level setting, bonus would be switching timezone from a dashboard.

My use case, servers are always UTC and logs are UTC, however we have people viewing dashboards from around the world and who are travelling.

We need to view the dashboards and logs based on different timezones depending on what we are doing, eg. If I am debugging sometime relative to my use I need it to be whatever timezone I am in however I don't always change my computer timezone when I travel because I use multiple clocks amd timezones. I need to be able to change to the timezone I am in quickly and easily without changing my system time.

I also need to view logs and metrics based on the key timezone for a project when reporting to a client, so I want to screenshot a graph but I want it showing EST for the client, I also want to compare the graphs to EST because it gives me insight into the usage in that timezones hours.

I also want to switch to and from UTC when I am comparing events and logs from other places on the server which are not in signoz, in this case its much easier if I switch back to UTC so I don't get lost or confused.

These are my core uses cases for timezone switching.

ankitnayan commented 1 week ago

@ahmadshaheer please note these down in the planning for timezone support

ahmadshaheer commented 1 week ago

@ahmadshaheer please note these down in the planning for timezone support

@ankitnayan, the solution proposed in the PRD can support @micahnz's use cases.

ahmadshaheer commented 4 days ago

EPIC: https://github.com/SigNoz/signoz/issues/2723