Hey there,
There is no built in way to do this at the moment, and it has come up several times for folks to be able to see the wall time of a Horde job, and as you’ve indicated there are challenges in determining what that would. This is certainly something I could look at, but I can’t speak to when we would be able to offer a timeline on it.
One thing I’d probably mention/poke at is, what’s the goal here? Whilst it is difficult to account for end to end time (merely due to resource contention), I think there are still some valuable data to be learned on summed step time - agent compute time used for a job. Furthermore, an end to end time inclusive of resource contention waits is still insightful, as it shows the “user perceptible impact”. With these two metrics, I think you can generally answer a couple of key questions like:
- Is a job agent-expensive from a summed step perspective
- Is a job taking long for a P95 metric?
If these types of metrics sound reasonable, I’m happy to add them to my backlog or review a PR.
Kind regards,
Julian