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

ASF subversion and git services commented on SOLR-15753:
--------------------------------------------------------

Commit 8784f70f6755ef348b5db1ed78d7bfe3f090826a in solr's branch 
refs/heads/main from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=8784f70f675 ]

SOLR-15753: Ensure v2 API requests are logged (#1738)

Prior to this commit, no request logging existed for v2 API calls.

This commit adds request logging for v2 requests, via a JAX-RS
"post-request filter".  In an attempt to maintain compatibility with
existing logging dashboards, v2 logging uses the same HttpSolrCall and
SolrCore.Request loggers that are currently used to log v1 requests.

Some of the niceties built up around our v1 request logging are also
supported for v2: including the `logParamsList` parameter used to filter
which parameters get logged, and SLF4J "marker" support.

v2 logging also includes a stringified representation of the request body
for POST and PUT requests, which are more common in the v2 API.

> v2 calls should log params similar to current HttpSolrCall
> ----------------------------------------------------------
>
>                 Key: SOLR-15753
>                 URL: https://issues.apache.org/jira/browse/SOLR-15753
>             Project: Solr
>          Issue Type: Improvement
>          Components: v2 API
>            Reporter: Jason Gerlowski
>            Priority: Major
>              Labels: V2
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Currently, v1 API requests are logged out at INFO level in HttpSolrCall, 
> complete with all their API parameters. This logging is invaluable for a 
> variety of use cases (query gathering, perf analysis, etc.)
> We should ensure that the v2 API offers similar logging if possible.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to