wish tctl show workflow information --pdt show datetime with local timezone

[rmrf]

Is your feature request related to a problem? Please describe. tctl wf l command list workflow, but only display with UTC timezone

Describe the solution you'd like Local timezone will be greate

Describe alternatives you've considered How about use ENV to control whether use local timezone display, such as TEMPORAL_CLI_DISPLAY_TIMEZONE

Additional context n/a

[underrun]

From my perspective, operationally it's safer to stick with utc. Could you talk about your use cases a little? Is this just for human consumption when occasionally looking at what ran or is running out of curiosity? Or would you want it for serious investigation, analysis or automation?

[rmrf]

Recently we are trying to migrate our tasks of several teams to Temporal, it is kind of totally new framework to all of us.

During the mgiration, we heavily depends on the tctl cmd line to troubleshooting:

• When the activity/subworkflow start/end/terminate,
• Such as tctl wf showid sloslihive_22ee1a63-6390-4ddc-b897-a89729361485 --pdt and so on.

The correct Timezone will make this kind work less painful.

[rmrf]

https://github.com/rmrf/temporal/tree/timezone

Currently we are using above modified tctl binary which suport env TEMPORAL_CLI_DISPLAY_TIMEZONE for nice time display.

[feedmeapples]

Added to this tctl UX proposal https://github.com/temporalio/proposals/pull/35

[feedmeapples]

if you happen to have any other feedback, please consider checking the rest of the proposals and leaving some comments. It's highly valuable and appreciated. The proposals focus a UX improvements for tctl

[rmrf]

if you happen to have any other feedback, please consider checking the rest of the proposals and leaving some comments. It's highly valuable and appreciated. The proposals focus a UX improvements for tctl

Thanks, glad to know this proposals repo.

[samarabbas]

@feedmeapples looks like this would be addressed by the recent tctl work you are doing. Can you confirm?

[feedmeapples]

@rmrf could you elaborate on how having timezone flag makes it easier for your migration case. Do you want to know the exact time at specific timezone, or could something like relative time (ex. 2 hrs ago) make your migration simpler too? https://github.com/temporalio/proposals/pull/35/files#diff-fd43e76660a0644c8d5027ed26ef9dbb8086737f8145733070445413a18f4133R10

[rmrf]

@feedmeapples konwing the exact time at specific timezone is most valuable to us. We have two types of tasks migrating to Temperal

• Ad-hoc tasks, which the owner define the exact task start time on their app platform, the platform will trigger http call to wf starter web server, then collect the result and display on the platform
• Temporal cron type (such as run every minutes)

for the first one, exact time at specific timezone is meaning for to the owners, consider they are checking their app logs/metrics on kibana/grafana then cross compare with tctl's output, exact time at specific timezone is making this kind of work really easy.

recently we have setup the temporal web for the task owners, they are happy to have local timezone display on it (not every time display is local timezone, a lot of detail still in UTC, such as inside history tab, but for those one who don't like command line, it's a big help)

[rmrf]

If tempral wf/activity need to interactive with other existing service/app inside company, the time display locally as kibana/grafana/(other tools) will make them work better.

[feedmeapples]

@rmrf ok, i've updated the proposal to support specific timezones https://github.com/temporalio/proposals/pull/35#issuecomment-875922145