Thank you Andy, I was not aware of this option. It works as described.
However, it provides no information additional to the apache logs
(apache works in front of fuseki as reverse proxy). The content of POST
request (with the actual query) is not present in either log lines.
Relating the NCSA lines with the actual queries means a bit of guessing.
It would be great if I could see the IP as part of the "regular" log
lines, along with the query and the request number. The purpose would be
to identify the provenance of resource-intensive requests in our public
endpoints.
Is there any chance to achieve that?
Cheers, Joachim
On 15.08.23 11:43, Andy Seaborne wrote:
If you turn on the NCSA logging, there is a standard format logging
line output.
In the provided log4j2.properties, it is switched off by default:
logger.fuseki-request.level = OFF
so comment out that line and a NCSA log line is generated which
include X-Forwarded-For.
You can direct this to a separate file using log4j2.
For development/debugging, if you run with "-v", all the headers, for
request and response, are printed out.
Andy
On 15/08/2023 08:21, Joachim Neubert wrote:
Hi everybody,
is there a way to log the client ip address (in my case, particularly
the X-Forwarded-For as delivered by the proxy) in the fuseki log file?
Cheers, Joachim
--
Joachim Neubert
ZBW - Leibniz Information Centre for Economics
Neuer Jungfernstieg 21
22354 Hamburg, Germany
