Ticket #320
(closed enhancement: fixed)
Logging improvements
| Reported by: |
Joel |
Owned by: |
Joel
|
|
Priority:
|
major
|
Milestone:
|
Eraser 6.1/6.2
|
|
Component:
|
Core
|
Version:
|
|
|
Keywords:
|
|
Cc:
|
|
|
Blocked By:
|
#300 |
Blocking:
|
#275 |
|
Operating System:
|
|
Processor Architecture:
|
|
The logger is currently very involved when doing logging -- we need to instantiate new LogEntry structs, we need to initiate sessions etc. It's also very fickle about the validity of sessions. The Logging should be able to tolerate errors and should be more flexible.
The Last Sesssion timestamp is not reset after a session is completed; new messages go to the wrong session.
- The log should also include the statistics and result of an erase task.
Differentiate between "Completed with Errors" vs "Aborted with Errors" etc etc.
- What qualifies as errors?
What do errors imply? Do Errors mean that the target didn't complete? Do fatal errors mean that the entire task didn't complete?
Change History
