Enhancement #549
Agents need to give more informative error messages in the logs
| Status: | New | Start date: | 01/25/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Mary Laser |
% Done: | 0% |
|
| Category: | UI | |||
| Target version: | - | |||
| Rank: | 99 | Tester: |
Description
The agent logs do not contain enough information to determine what went wrong. Using an error code like 3 or agent code 12 does not indicate what the real error was. Saying only in the log that the agent failed is also not helpful when trying to figure out what the problem is or how it might be fixed.
The agents should give informative messages like 'file xxx not found', no permission to write to xxxx, can't schedule scheduler, go db error xxxx, etc...
History
Updated by Mary Laser over 1 year ago
- Target version changed from 2.0.0 to 2.0.1
Agreed. Especially useful when trying to determine failures. Bob has been preaching this every chance he gets. Since this enhancement affects all agents, we'll define/create an all-inclusive task to improve error reporting post-2.0.
Updated by Mary Laser 9 months ago
- Target version deleted (
2.0.1)
Updated by Bob Gobeille 8 months ago
- Rank set to 99
Change unranked issues to rank 99 so they show up in a ranking report at the bottom. Otherwise, they show up on top.