I believe for netlogger we also want to know job names - I don't recall if it was the physical, planned job name, or the logical DAX job name. (Mats, Gideon or Fabio would know.) For one of the two we can recycle the currently unused "derivation" option of kickstart. (In a new, config-file driven kickstart, we should have a section of arbitrary k=v-pair propagations. But that's besides the point of this task.)

This task would require potentially almost no C code change to kickstart, though its documentation should be updated to reflect the new usage. However, it would have some, hopefully minor, changes in the planner to add this option when generating kickstarted jobs. It should be similar to what is done with "magic comments" in seqexec. (Though I may want to review the seqexec comment option.) And potentially deeper changes are required in the tools that pick up the output record to propagate to netlogger.

Once we agree on the details, we should create 3 sub-tasks to reflect each portion: planner changes, kickstart changes, monitord changes.