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

Shawn Heisey commented on SOLR-4132:
------------------------------------

Messages from the new category could be at slf4j's trace level so that when 
logging all categories at INFO or DEBUG, you won't see duplicate messages.
                
> Special log category for announcements, startup messages
> --------------------------------------------------------
>
>                 Key: SOLR-4132
>                 URL: https://issues.apache.org/jira/browse/SOLR-4132
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 4.0
>            Reporter: Shawn Heisey
>             Fix For: 4.1, 5.0
>
>
> When logging at WARN (log4j) or WARNING (jul), Solr startup logs nothing or 
> next to nothing.  I would like to be able to include some informational 
> messages in the log so that I can see that something's happening, and that 
> Solr is ready for use.  It would probably be wrong to set the level of such 
> things to WARN, because they aren't warnings.
> An alternate plan would be to create a special log category, which could be 
> set to INFO in log4j.properties or logging.properties.  David Smiley 
> suggested org.apache.solr.announcement.
> At a minimum, the new category should have messages for initial startup, core 
> creation, all initialization finished, and shutdown.  There may be other 
> things that should be included too.  It may even be a good idea to have 
> subcategories.  Some initial ideas I've thought of:
> org.apache.solr.announcement.startup
> org.apache.solr.announcement.shutdown
> org.apache.solr.announcement.init
> org.apache.solr.announcement.misc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to