[
https://issues.apache.org/jira/browse/SOLR-16044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718921#comment-17718921
]
Jan Høydahl commented on SOLR-16044:
------------------------------------
[~hossman] You recently discussed logging levels env.vars and proposed to
inject sysprops into log4j2.xml directly. Would it make sense to inject the
level from {{SOLR_LOG_LEVEL}} / {{-Dsolr.log.level}} into the ROOT logger tag,
and invent a separate sysprop for SolrCore, which defaults to INFO, but can be
changed to mute request logs? Still feel it would be beneficial to be able to
control SolrCore logs separately from {{SolrCore.SlowRequest}} and
{{SolrCore.Request}} though...
> SlowRequest logging disabled if SolrCore logger set to ERROR
> ------------------------------------------------------------
>
> Key: SOLR-16044
> URL: https://issues.apache.org/jira/browse/SOLR-16044
> Project: Solr
> Issue Type: Bug
> Components: logging
> Environment: Solr 8.4
> Reporter: Jan Høydahl
> Priority: Major
>
> If someone sets ROOT logger to ERROR, then {{SolrCore}} class will also be
> set to ERROR, and even if {{SolrCore.SlowRequest}} level is set to INFO, no
> logs will be written to {{{}solr_slow_requests.log{}}}.
> Some debugging revealed that changing log level of {{SolrCore}} to WARN fixes
> it. This suggests that since {{SlowRequest}} is not a real class but just a
> logger name, it is still subject to the log level of {{SolrCore}}.
> I suppose that the same will be true for {{SolrCore.Request}} logging.
> One solution could be to create a real class for SlowRequest logging. Another
> solution could be to explicitly set {{SolrCore}} level in {{log4j2.xml}} so
> that it does not follow the ROOT level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
