[YADE-240] Rewrite YADE logging for better overview and debugging - SOS JIRA

XML

Word

Printable

Details

Type: Feature
Status: Released (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 1.7.4
Fix Version/s: 1.9
Component/s: YADE Client
Labels:
None

Description

The current YADE logging severely lacks traceability, e.g.

clarity about parameters used i.e. wrong banner
connection direction for operations SOURCE-->TARGET
sequence which YADE execute connection/operations
logging of operations performed i.e. connected to server, start transfer etc
readability
debug levels
if an error occurred then the original error message should log at the end (without stracktrace in info level)

Attachments

Issue Links

is duplicated by

YADE-65 Logging of jump_host activities

Dismissed

is required by

YADE-227 Send TCP/UDP signal to the YADE Background Service if operation failed

Released

relates to

YADE-232 YADE info log messages should be more concise

Released

Activity

People

Assignee:: Oliver Haufe

Reporter:: Mahendra Patidar

Resolver:: Mahendra Patidar

Approver:: Mahendra Patidar

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Due:: 31/Mar/15

Created:: 26 January 2015 11:48

Updated:: 24 October 2015 15:24

Resolved:: 02 April 2015 16:28

Time Tracking

Estimated:

3d

Remaining:

1d

Logged:

2d