#3348 [Core feature] Enhance task logging template utils for start/finish time Issue created by andrewwdye Motivation: Why do you think this is important? Flyteplugins provides default task logging support for Cloudwatch and Stackdriver; however, the links don't include start/finish times. Depending when the links are followed, the user may need to adjust time filters in the log viewer, leading to initial confusion over missing logs and adding an unnecessary step. Template params for

{{ .podUnixStartTime }}

and

{{ .podUnixFinishTime }}

are provided; however. they are incompatible with at least Cloudwatch and Stackdriver. Cloudwatch expects time queries in unix timestamp using millisecond granularity and Stackdriver expects time queries in RFC3339 or ISO 8601 formats. Goal: What should the final outcome look like, ideally? Flyte task log links should contain time specific references based on the task's start time (and end time if available). Describe alternatives you've considered Require the user to manually filter to the task timeframe Propose: Link/Inline OR Additional context One option is to introduce new template params for

PodUnixMsecStartTime

and

PodTimestampStartTime

(and their Finish counterparts), corresponding to unix milliseconds and RFC 3339, respectively. As part of this change we should update the log link to use the container end time if available. Today it is hardcoded to

now()

. Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte