[YANGTOOLS-797] Yangtools log when failing to assemble sources needs to be at a higher level Created: 14/Jul/17 Updated: 10/Apr/22 |
|
| Status: | Confirmed |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Giles Heron | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 8856 | ||||||||
| Description |
|
The module SharedSchemaContextFactory.java logs "Failed to assemble sources" at DEBUG level. Surely this should be at INFO or WARN or something? Took me ages to find this log - had to enable Yangtools logging at DEBUG (resulting in massive logs of info I didn't need). If it had been at INFO I'd have seen it immediately... |
| Comments |
| Comment by Robert Varga [ 01/Aug/17 ] |
|
This is a conflicting requirement, see BUG-7925. We cannot raise them by default until BUG-7925 is addressed, as we would go back to massive false positives during controller startup. You certainly can enable debug logs only on that class, which should fix the problem of large logs. |
| Comment by Giles Heron [ 01/Aug/17 ] |
|
so how do we find a way to make the logs usable by regular users? This is probably the biggest usability issue in ODL. Enable TRACE logging on the whole platform and use an ML back end? (ML is "magic", it will solve all our problems if only we give it enough data, lol). |