Problem: Simulation produces event log messages in an inconsistent format. The logging also has different levels of verbosity, sometimes too detailed, other times skipping over critical steps in the execution of a request.
Desired functionality:
- Maintain a single log message structure. E.g., [time] [file name:LoC] [Component.ID] [Process] [ReqID] | Message body
- Consistent usage of log message priorities to easily increase/decrease verbosity. For example:
- ERROR: simulation breaking event and early stop.
- WARNING: simulation results potentially affected.
- INFO: per request-completion metrics
- DEBUG: log message for event required to track the progress of each request through each component
Problem: Simulation produces event log messages in an inconsistent format. The logging also has different levels of verbosity, sometimes too detailed, other times skipping over critical steps in the execution of a request.
Desired functionality:
- ERROR: simulation breaking event and early stop.
- WARNING: simulation results potentially affected.
- INFO: per request-completion metrics
- DEBUG: log message for event required to track the progress of each request through each component