[ https://issues.apache.org/jira/browse/SOLR-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837860#comment-13837860 ]
Shikhar Bhushan commented on SOLR-5505: --------------------------------------- Hi Ryan, * If the loggerName attribute is missing, it defaults to the fully-qualified class name of LoggingInfoStream (see default value used for getting the attribute). * I will update the example solrconfig.xml, good call! * Even if the logs are being sent to the same file, the logger name is almost always part of the formatter configuration. For the solrconfig.xml perhaps a good example would be {{<infoStream loggerName="org.apache.solr.update.LoggingInfoStream.${solr.core.name}">}} (I _think_ that actually will substitute core name correctly, will check...). > LoggingInfoStream not usabe in a multi-core setup > ------------------------------------------------- > > Key: SOLR-5505 > URL: https://issues.apache.org/jira/browse/SOLR-5505 > Project: Solr > Issue Type: Bug > Affects Versions: 4.6 > Reporter: Shikhar Bhushan > Attachments: SOLR-5505.patch > > > {{LoggingInfoStream}} that was introduced in SOLR-4977 does not log any core > context. > Previously this was possible by encoding this into the infoStream's file path. > This means in a multi-core setup it is very hard to distinguish between the > infoStream messages for different cores. > {{LoggingInfoStream}} should be automatically configured to prepend the core > name to log messages. -- This message was sent by Atlassian JIRA (v6.1#6144) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org