We used logs to export information on worker choices for post-processing. These are used for specific papers/experiments and afterwards we are currently left with three options:
- Delete the logging lines from the codebase (making re-production hard)
- Create boolean configuration settings and code fence them
- Do nothing and bloat the log files with extraneous information
A targeted way to enable these via the Logging configuration would be ideal. Log events have a target, (e.g. iluvatar_worker_library::services::resources::gpu) member corresponding to the module & file the log message was in.
Possible solution:
We could set experimental log statements like these to debug or trace and create a custom Layer that allows them to bypass the log level filter if target matches given configuration.
We used logs to export information on worker choices for post-processing. These are used for specific papers/experiments and afterwards we are currently left with three options:
A targeted way to enable these via the Logging configuration would be ideal. Log events have a
target, (e.g.iluvatar_worker_library::services::resources::gpu) member corresponding to the module & file the log message was in.Possible solution:
We could set experimental log statements like these to
debugortraceand create a custom Layer that allows them to bypass the log level filter iftargetmatches given configuration.