Quite often, classes end up adding information about the recipe/task the messages are associated with, and they do so quite often, and in inconsistent ways. I think there would be value in the bitbake UI associating all log messages generated by a task with that recipe+task, so the user always knows where they came from, and the code generating the messages can stop doing so themselves in inconsistent ways.

See https://gist.github.com/kergoth/50af1ca12692d39f0338 for one prototype for knotty, though it might be cleaner to do it in a subclass of the BBLogFormatter rather than modifying the message in the event loop.