[JENKINS-43788] multi-entry logging

Single error/stacktrace is not very useful. It would be more useful to bundle some logger with logging levels tied to log file.

Use case: docker provisioning has multiple places with different logging information and it should be available/known before stacktrace, not only single stacktrace.  

---
Originally reported by integer, imported from: multi-entry logging

• status: Open
  
• priority: Minor
  
• component(s): cloud-stats-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 20251216-182730
  

Raw content of original issue

Single error/stacktrace is not very useful. It would be more useful to bundle some logger with logging levels tied to log file.


Use case: docker provisioning has multiple places with different logging information and it should be available/known before stacktrace, not only single stacktrace.  

Start by reading the existing cloud provisioning error and stacktrace handling, with particular attention to Docker provisioning and its multiple logging points. Define how a logger would bundle those entries, associate logging levels with a log file, and make the information available before the final stacktrace.

Written by the indexing model from the issue text.