lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-11453) Create separate logger for slow requests
Date Sun, 06 May 2018 17:43:00 GMT

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

Shawn Heisey commented on SOLR-11453:
-------------------------------------

[~ralph.goers@dslextreme.com], thanks for the docs.  There is a lot of information there,
but I'm not sure that there is enough information there for *ME* to figure out how to write
a script to look at sysprops and determine whether certain loggers will be sent to the main
file or to their own file(s).

I see in the docs where a list of three parameters is sent to the script, one of which is
logEvent.  Is there a reference for everything contained within those parameters?

Is javascript the recommended language choice?  I'm wondering about its performance, mostly.
 I don't want to introduce really slow components into the logging.  One of the examples on
that doc page says javascript, but appears to actually include Java code.  If my interpretation
of that example is correct, does *that* perform well?

If using javascript directly and not including Java code, are sysprops available?  If so,
how are they accessed?

> Create separate logger for slow requests
> ----------------------------------------
>
>                 Key: SOLR-11453
>                 URL: https://issues.apache.org/jira/browse/SOLR-11453
>             Project: Solr
>          Issue Type: Improvement
>          Components: logging
>    Affects Versions: 7.0.1
>            Reporter: Shawn Heisey
>            Assignee: Shawn Heisey
>            Priority: Minor
>         Attachments: SOLR-11453.patch, SOLR-11453.patch, SOLR-11453.patch, SOLR-11453.patch,
slowlog-informational.patch
>
>
> There is some desire on the mailing list to create a separate logfile for slow queries.
 Currently it is not possible to do this cleanly, because the WARN level used by slow query
logging within the SolrCore class is also used for other events that SolrCore can log.  Those
messages would be out of place in a slow query log.  They should typically stay in main solr
logfile.
> I propose creating a custom logger for slow queries, similar to what has been set up
for request logging.  In the SolrCore class, which is org.apache.solr.core.SolrCore, there
is a special logger at org.apache.solr.core.SolrCore.Request.  This is not a real class, just
a logger which makes it possible to handle those log messages differently than the rest of
Solr's logging.  I propose setting up another custom logger within SolrCore which could be
org.apache.solr.core.SolrCore.SlowRequest.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message