[teiid-issues] [JBoss JIRA] Updated: (TEIID-386) Improve error reporting to NOT include stack traces when appropriate and logging level < Detail

[Steven Hawkins (JIRA)]

     [ https://jira.jboss.org/jira/browse/TEIID-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-386:
---------------------------------

          Component/s: Common
                           (was: Query Engine)
        Fix Version/s: 6.1.0
    Affects Version/s: 6.0.0
             Priority: Minor  (was: Major)


Teiid is much better about the amount of stacktraces that will be logged, which lessens the need for this defect.

Are you saying that you would like a separate logging configuration item that says "show stacktraces for logs at log level"? 

It seems like this only applies for logs at the WARNING, INFO, and DETAIL levels.  As a matter of practice, there are very few places where a exception logged at the INFO or DETAIL levels.  But you are correct that we don't differentiate user generated parsing exceptions, validation exceptions, etc. when they get logged at the WARNING level - their full stacktrace is still shown.  Would it be sufficient in these cases to separate the logging of the error message as a warning and to log the stacktrace as a detail?

> Improve error reporting to NOT include stack traces when appropriate and logging level < Detail
> -----------------------------------------------------------------------------------------------
>
>                 Key: TEIID-386
>                 URL: https://jira.jboss.org/jira/browse/TEIID-386
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Common
>    Affects Versions: 6.0.0
>         Environment: Any and all
>            Reporter: Paul Nittel
>            Assignee: Steven Hawkins
>            Priority: Minor
>             Fix For: 6.1.0
>
>
> The server presently adds stack traces with reckless abandon. It seems like anything that upsets the software yields at least one stack trace.
> I'd like to propose that "human errors", like parsing SQL statements, return just an error (in the logs, too). If the server is set to log at Detail or Trace, then crank out the stack traces if that's necessary. Logs that show only important stuff are more valuable.
> (I looked in Teiid and didn't see an entry like this. If it's a dup, that's fine, as long as the stack trace deluge is remedied.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira