You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to trace the execution of jobs from the job creator perspective. Our long term goal is to implement a job trace across the entire job lifecycle. As a starting point, let's implement a trace on the job creator only that captures success/failure, time spent running a job, requested module, and other relevant details.
This information will help us debug issues on the job creator. It will also give us useful product metrics such as average time spent running a job per module.
The job creator job run is split across a couple of functions in its control loop. We will likely need a way to associate a couple of small traces to see a nice overall output.
The text was updated successfully, but these errors were encountered:
We would like to trace the execution of jobs from the job creator perspective. Our long term goal is to implement a job trace across the entire job lifecycle. As a starting point, let's implement a trace on the job creator only that captures success/failure, time spent running a job, requested module, and other relevant details.
This information will help us debug issues on the job creator. It will also give us useful product metrics such as average time spent running a job per module.
The job creator job run is split across a couple of functions in its control loop. We will likely need a way to associate a couple of small traces to see a nice overall output.
The text was updated successfully, but these errors were encountered: