I spent some time cleaning up the Log output, specifically reducing redundant labeling. On the way it became clear that the real place for most of these logs is in the Observability modules, not on the runner itself. This has proven to be a nice refactor, clarifying the purpose of the Observability mobule and distilling the runner logic by removing the fluff required to inform users of the state.
This changes the log output:
The overseer boot message used to be:
INFO - mosquito.runners.overseer.4315742080: Overseer<4315742080> is starting
Now the message is simply:
INFO - mosquito.overseer: starting
Similarly, messages from QueueList, Executor, Coordinator, now lack the .runners. segment of the tag. Where a runner is likely to be the only instance of that runner within a mosquito process (as with overseer exemplified above) the object id is no longer part of the tag either.
I spent some time cleaning up the Log output, specifically reducing redundant labeling. On the way it became clear that the real place for most of these logs is in the Observability modules, not on the runner itself. This has proven to be a nice refactor, clarifying the purpose of the Observability mobule and distilling the runner logic by removing the fluff required to inform users of the state.
This changes the log output:
The overseer boot message used to be:
INFO - mosquito.runners.overseer.4315742080: Overseer<4315742080> is startingNow the message is simply:INFO - mosquito.overseer: startingSimilarly, messages from QueueList, Executor, Coordinator, now lack the
.runners.segment of the tag. Where a runner is likely to be the only instance of that runner within a mosquito process (as withoverseerexemplified above) the object id is no longer part of the tag either.