From within a task, is it possible to get the

created_at

and

started_at

attributes? Or would that require a call to FlyteAdmin?

As that data is stored on the database, I think it will require a call to FlyteAdmin

yeah. what would this be used for?

I’m aggregating all of the data from FlyteDecks timeline into a single CSV file to quantify performance drift over time. One thing it doesn’t captured is time queued, which we’ve had some issues with due to our node pool and IP addresses

this is performance drift of flyte itself?

it’s mostly for our tasks, but the queued timing is for Flyte/our cluster itself yes

i feel like these should be considered separately, though i don’t have good advice on how.

we could write a small helper function to profile the last X executions, but was hoping the runtimes (and time queued) could be an artifact of the execution itself