How to update UTC to local time in alerts and reports logs?

[devysh1907]

How to update UTC to local time in alerts and reports logs?

[dosubot[bot]]

To update UTC to local time in alerts and reports logs, you can modify the moment formatting in the ExecutionLog component. Currently, the code formats the date using moment(new Date(scheduledDttm)).format('YYYY-MM-DD hh:mm:ss a') and moment(new Date(startDttm)).format('YYYY-MM-DD hh:mm:ss a'). To convert these to local time, you can use moment.utc() to parse the date and then use .local() to convert it to local time:

{
  Cell: ({
    row: {
      original: { scheduled_dttm: scheduledDttm },
    },
  }: any) =>
    moment.utc(new Date(scheduledDttm)).local().format('YYYY-MM-DD hh:mm:ss a'),
  accessor: 'scheduled_dttm',
  Header: t('Scheduled at (Local)'),
},
{
  Cell: ({
    row: {
      original: { start_dttm: startDttm },
    },
  }: any) =>
    moment.utc(new Date(startDttm)).local().format('YYYY-MM-DD hh:mm:ss a'),
  Header: t('Start at (Local)'),
  accessor: 'start_dttm',
},

This change will ensure that the timestamps are displayed in the local time zone instead of UTC ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[devysh1907]

@dosu
I am using helm chart to deploy supert, so how to do that using helm chart

[dosubot[bot]]

To update the time zone settings in a Superset deployment using a Helm chart, you would typically need to adjust the configuration files or environment variables that control time zone settings. However, the specific details on configuring time zones or localization settings in the Superset Helm chart are not directly available in the provided documentation.

In general, you can try the following approach:

1. Environment Variables: Check if there are any environment variables related to time zone settings that you can configure. You can add these to the extraEnv section of your values.yaml file in the Helm chart.

2. Custom Configuration: If Superset allows for custom configuration files, you might be able to mount a custom configuration file that sets the desired time zone. This can be done by using the extraVolumes and extraVolumeMounts options in the Helm chart to include your custom configuration.

3. Application Code: If the time zone needs to be adjusted in the application code (like the ExecutionLog component), you might need to build a custom Docker image with your changes and use that image in your Helm deployment.

These are general strategies, and the exact implementation may vary based on the specific requirements and capabilities of the Superset Helm chart.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}