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

Jan Høydahl commented on SOLR-14142:
------------------------------------

So here's a PR that does this: [https://github.com/apache/solr/pull/542]

It will log on INFO if logging is enabled and explicitly configured, else log 
WARN.

The WARN log looks like this in the Admin UI:

!Skjermbilde 2022-01-19 kl. 11.33.51.png!

> Enable jetty's request log by default
> -------------------------------------
>
>                 Key: SOLR-14142
>                 URL: https://issues.apache.org/jira/browse/SOLR-14142
>             Project: Solr
>          Issue Type: Improvement
>          Components: logging
>            Reporter: Robert Muir
>            Assignee: Jan Høydahl
>            Priority: Major
>             Fix For: 9.0
>
>         Attachments: SOLR-14142.patch, SOLR-14142.patch, Skjermbilde 
> 2022-01-19 kl. 11.33.51.png
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> I'd like to enable the jetty request log by default.
> This log is now in the correct directory, it no longer uses the deprecated 
> mechanisms (it is asynclogwriter + customformat), etc. See SOLR-14138.
> This log is in a standard format (NCSA) which is supported by tools 
> out-of-box. It does not contain challenges such as java exceptions and is 
> easy to work with. Without it enabled, solr really has insufficient logging 
> (e.g. no IP addresses).
> If someone's solr gets hacked, its only fair they at least get to see who did 
> it.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to