Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Error handling improvement #29

Closed
ywang19 opened this issue Apr 11, 2013 · 3 comments
Closed

Error handling improvement #29

ywang19 opened this issue Apr 11, 2013 · 3 comments
Assignees
@yllions
Labels
2 - Working enhancement
Milestone
0.4.1

Comments

@ywang19
Copy link
Contributor

ywang19 commented Apr 11, 2013

A few areas need improve to help quicker trouble shooting:

  1. If workload gets failed, need identify which part causes the failure.
  2. while the target Amplistor doesn’t enable the port. There is no warning in log.
  3. Check status of drivers if stuck/ crashed before commencement of test
This was referenced Apr 11, 2013
Closed
Closed
Closed
@ywang19
Copy link
Contributor Author

ywang19 commented Dec 18, 2013

  • error classification and statistics, e.g, to show the count of error code 404, 501...
  • squeeze similar exception call stack to avoid huge duplicated information in log
  • print out what container/object is in access when error is occurred to help trouble shooting.

@ghost ghost assigned tsg- Dec 18, 2013
@ywang19
Copy link
Contributor Author

ywang19 commented Jan 28, 2014

. determine messages should be printed out at different log level.

@ywang19 ywang19 assigned yllions and unassigned tsg- Aug 27, 2014
@ywang19
Copy link
Contributor Author

ywang19 commented Nov 7, 2014

This is a scattering enhancement in with a few commits with other fixes.

@ywang19 ywang19 closed this as completed Nov 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yllions yllions

Labels
2 - Working enhancement
Projects
None yet
Milestone
0.4.1
Development

No branches or pull requests
3 participants
@tsg- @ywang19 @yllions