[
https://issues.apache.org/jira/browse/SOLR-16582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688087#comment-17688087
]
Jason Gerlowski edited comment on SOLR-16582 at 2/13/23 6:58 PM:
-----------------------------------------------------------------
[~patson] [~noblepaul] - this is a nice little ops feature, but how is anyone
going to use it without it documented anywhere? Even if there's not a great
place for it in the ref-guide, at the very least it could be a commented out
example in our log4j config, couldn't it? Or as a note in CHANGES.txt? Would
you guys mind documenting this somewhere?
Also, should this ticket be closed? What is the Fix Version?
was (Author: gerlowskija):
[~patson] [~noblepaul] - this is a nice little ops feature, but how is anyone
going to use it without it documented anywhere? Even if there's not a great
place for it in the ref-guide, at the very least it could be a commented out
example in our log4j config, couldn't it? Would you guys mind documenting this
somewhere?
> Add marker to request logging of SolrCore#execute
> -------------------------------------------------
>
> Key: SOLR-16582
> URL: https://issues.apache.org/jira/browse/SOLR-16582
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: main (10.0)
> Reporter: Patson Luk
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Logs can somethings be a bit too noisy on SolrCore#execute which prints info
> on each response.
> In our usage, `/get` and `/replication` are too verbose that we want to skip
> logging those 2 while keeping response logging for rest of the requests.
> It would be nice to add a "marker" with the path of the request so that user
> can tune logging behavior per request handler (path).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
