I would like to expore using OpenTelemetry and other options including building our very own and simple correlation/tracing for image builder components (ib service, composer, workers, osbuild) in order to report build progress back to the user in detailed manner including possible error details.

We briefly discussed it within the team and here is the feedback:

• Simon: otel is heavyweight, we should consider alternatives +1 (lzap)
• Sanne: lets cleanup correlation and use just one field
• Florian: likes the ability to use otel UI at some point in the future
• Sanne: jobs has dependencies and it is sometimes a problem, having a separate trace_id field sounds good
• Simon: trace_id should be generated at the very beginning (entry point)

I would like to explore technical debt of replacing unmaintained logrus with slog (part of Go standard library) too.