The telemetry in the CLI was designed for job-runner, where we're mostly interested in the performance of a single job. But when looking at the telemetry for the CLI, it would also be useful to see the duration of an entire job request, because that gives a better picture of the user experience.
We could do this by creating a span for the whole opensafely run command, which is the parent of each individual job span.
The telemetry in the CLI was designed for job-runner, where we're mostly interested in the performance of a single job. But when looking at the telemetry for the CLI, it would also be useful to see the duration of an entire job request, because that gives a better picture of the user experience.
We could do this by creating a span for the whole
opensafely runcommand, which is the parent of each individual job span.