Change Details

### Problem Statement: While refactoring the way changes are dispatched from Wikidata to client wikis [0] from using maintenance scripts to using jobs, it became clear that the options to //observe// jobs aren't exactly great. That is a problem, because this refactoring is touching a very vital part of Wikimedia infrastructure and we're now working somewhat in the dark. It would make future maintenance and debugging work much easier if it were easier to observe what jobs are being created and what they are doing. That is, I want to be able to **//see//** what jobs are actually running and doing, instead of just reasoning from the code and crossing my fingers when I make changes. ### Idea for improving things: I would like to see some tree-like //visualization// starting from a (debug) request that shows: * What jobs were created in that request? * Which other jobs were triggered by those? (and so on, -> tree) * What were the (debug- or even trace-level?) logs of each job? * How long did each of these jobs take to complete and when did they run? (-> Timeline view?) * Maybe: What hooks were called in the context of each job? [0]: See T48643, T272356, and #wikibase_change_dispatching_scripts_to_jobs in general

### Problem Statement: While refactoring the way changes are dispatched from Wikidata to client wikis [0] from using maintenance scripts to using jobs, it became clear that the options to //observe// jobs aren't exactly great. That is a problem, because this refactoring is touching a very vital part of Wikimedia infrastructure and while the observability of the old dispatch mechanism was (is) quite bad, we're now still working mostly in the dark. It would make future maintenance and debugging work much easier, if it were simpler to observe what jobs are being created and what they are doing. That is, I want to be able to look and **//see//** what jobs are actually running and doing, instead of just reasoning from the code and crossing my fingers when I make changes. ### Idea for improving things: I would like to see some tree-like //visualization// starting from a (debug) request that shows: * What jobs were created in that request? * Which other jobs were triggered by those? (and so on, -> tree) * What were the (debug- or even trace-level?) logs of each job? * How long did each of these jobs take to complete and when did they run? (-> Timeline view?) * Maybe: What hooks were called in the context of each job? [0]: See T48643, T272356, and #wikibase_change_dispatching_scripts_to_jobs in general

### Problem Statement: While refactoring the way changes are dispatched from Wikidata to client wikis [0] from using maintenance scripts to using jobs, it became clear that the options to //observe// jobs aren't exactly great. That is a problem, because this refactoring is touching a very vital part of Wikimedia infrastructure and wwhile the observability of the old dispatch mechanism was (is) quite bad, we're now still working somewhatmostly in the dark. It would make future maintenance and debugging work much easier, if it were easiersimpler to observe what jobs are being created and what they are doing. That is, I want to be able to look and **//see//** what jobs are actually running and doing, instead of just reasoning from the code and crossing my fingers when I make changes. ### Idea for improving things: I would like to see some tree-like //visualization// starting from a (debug) request that shows: * What jobs were created in that request? * Which other jobs were triggered by those? (and so on, -> tree) * What were the (debug- or even trace-level?) logs of each job? * How long did each of these jobs take to complete and when did they run? (-> Timeline view?) * Maybe: What hooks were called in the context of each job? [0]: See T48643, T272356, and #wikibase_change_dispatching_scripts_to_jobs in general