This will require some changes to our logging setup in order to save our own logs and upload them later. Release engineering would like this for transparency.
I think the problem @jkaluza mentioned was that MBS keeps global logs - but there's no easy way to filter only logs applicable to a specific module build? Might be remembering wrong
We would have to wrap log.info(...) and others to take the module build id and replace log.info and others with these wrappers. Not hard to do, but rather boring thing :)
log.info(...)
Or better plan:
Get the module build id in the MBSConsumer.process_message and set it to global variable. Subclass the logging.getLogger() class, set the "log" in init.py to it and wrap the info/debug/error/exception methods so they handle the module build id from that global variable and append the log message also to per-module-build-id log as well as to normal logging endpoint.
Looks like this was taken on in a few PRs elsewhere: #599 and #601. Can this be closed?
Maybe close this once we merge #601?
Metadata Update from @ralph: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.