Logger injected into all tasks
@denolf I discussed with @payno and you should make another issue for this and describe the use case. Strictly speaking python logging is not ewoks' business. But it would be easy to use the
execinfo
mechanism that registers handlers to the ewoks event logger for the root logger as well (e.g. provide a flag which says this handler is only for ewoks events or for all python logging).
Follow on from #12 (closed), it would be nice if we could reuse the execinfo
mechanism to inject a logging handler in to all tasks with at least job_id populated as extra metadata. This allows you to track processing log messages in a single location originating from multiple beamlines and being executed over multiple machines.
This is how things are currently set up with zocalo, graylog handler is injected into each task of the graph. Maybe my use case is weird and the rest of you have other ways to handle this @svensson @payno ?