You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2014/10/31 17:29:33 UTC

[jira] [Commented] (HBASE-12396) Document suggested use of log levels in dev guide

    [ https://issues.apache.org/jira/browse/HBASE-12396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192008#comment-14192008 ] 

Sean Busbey commented on HBASE-12396:
-------------------------------------

Personally, I like the focus on "INFO and more severe is for operator use."

* ERROR if at all possible should include a plain description of the problem and an action the operator can take to either correct or troubleshoot
* Stack traces should be rare above DEBUG. We allow changing the level of a particular logger at run time, if an operator needs that level of detail they can alter the level (we should improve the docs on doing this).
* I think a good heuristic for DEBUG v TRACE is if you need multiple messages that show the flow of control within part of the codebase, you ought to be logging at TRACE. 

> Document suggested use of log levels in dev guide
> -------------------------------------------------
>
>                 Key: HBASE-12396
>                 URL: https://issues.apache.org/jira/browse/HBASE-12396
>             Project: HBase
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Sean Busbey
>            Priority: Minor
>
> Right now we don't provide any guidance on appropriate use of log levels, which leads to inconsistent use and in some cases exacerbating problems for tests and troubleshooting (see HBASE-12395). We should add a section on suggested use of log levels to the guide.
> Some related reading
> * [a good ops-focused blog post on levels|http://watchitlater.com/blog/2009/12/logging-guidelines/]
> * [another, focused on devs|http://www.codeproject.com/Articles/42354/The-Art-of-Logging]
> * [guidelines from a user on stackoverflow (that I like)|http://stackoverflow.com/a/2031209] also has some good discussion.
> * [extended logging discussion with some level use guidelines|http://www.javacodegeeks.com/2011/01/10-tips-proper-application-logging.html]
> * [guidelines for Atlassian devs|https://developer.atlassian.com/display/CONFDEV/Logging+Guidelines]
> * [guidelines for OpenStack devs|https://wiki.openstack.org/wiki/LoggingStandards]
> * [the Kafka dev guide|http://kafka.apache.org/coding-guide.html] has a good section on their use titled "Logging"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)